IT Support request template

When someone files an IT support request, the speed of the fix usually depends on the quality of the first message. A ticket that says “internet broken, please help” sends an agent on a guessing game. A ticket that names the device, the symptom, the priority and the steps already tried can be triaged and routed in seconds. This IT support ticket template gives your Jira Service Management desk a single, consistent intake form so every request arrives ready to act on. Copy the template above straight into a Jira issue, or read on for what to capture, how to categorize and prioritize a ticket, how routing works, and how to turn the structure into a reusable template with Process Templates for Jira.

What this template captures and why

In IT Service Management, support requests are an everyday occurrence: a hardware failure, a software glitch, a forgotten password, a flaky network. The teams that resolve them fastest are the ones that capture the same details every time. A standardized “Get IT Help” template, used as a service request template across the desk, makes that automatic, so every request is documented consistently and is easy to track, prioritize and address.

The template covers four things a service desk always needs to know:

• Who is asking, so the agent can follow up without hunting through the directory.
• What is wrong, in enough detail to reproduce or understand the issue.
• How urgent it is, separated into priority and business impact so triage is honest.
• What has already been tried, so the agent does not repeat the requester’s first 20 minutes.

Field-by-field breakdown

• Summary is the one-line headline that shows in every queue and report. Keep it specific: “Cannot connect to office Wi-Fi on MacBook Pro” beats “Wi-Fi problem”.
• Requester contact information captures the name, email and phone of the person who needs help. Useful when the reporter logs a ticket on behalf of a colleague.
• Description is the long-form account of the issue, including context, symptoms and any exact error messages. Verbatim error text is gold for diagnosis.
• Category is a dropdown (Hardware, Software, Account, Network, Email) that drives routing. Pair it with Jira Automation to push the ticket straight to the right specialist queue.
• Priority ranges from Critical to Low and sets the order agents work in.
• Impact describes the effect on business operations, from a whole team blocked down to a cosmetic annoyance. Splitting impact from priority stops every ticket from being marked “urgent”.
• Affected systems lists the device, application or service involved, ideally with an asset tag so hardware is identifiable.
• Steps to reproduce is a short checklist of the actions that trigger the problem, which lets the agent confirm the fault rather than ask for it.
• Steps already tried records the requester’s own troubleshooting so the agent starts where they left off.
• Supporting attachments holds screenshots or log files that make a 10-minute diagnosis a 1-minute one.

Ticket categorization: request types and categories

Categorization is the first decision on every help desk ticket, because everything downstream depends on it: which queue owns the ticket, which automation rule fires, which SLA applies and which dashboards count it. The Category dropdown on this template gives the desk a fixed vocabulary instead of free text that no report can group.

A practical starting set for an internal help desk ticket template is:

• Hardware covers laptops, monitors, docks, phones and peripherals: anything physical that fails or needs provisioning.
• Software covers application errors, license requests and install or update problems.
• Account covers password resets, group membership, onboarding and offboarding, and access requests.
• Network covers Wi-Fi, VPN, connectivity and bandwidth issues.
• Email covers mailbox, distribution-list and mail-flow problems.

Two habits keep categories useful. First, make Category required, so no ticket lands with a blank that forces manual triage. Second, keep the list short. A dozen overlapping categories slow the requester down and blur your reporting; five clear ones route cleanly. If you also expose request types in your JSM portal, map each portal request type to one category here so the IT support request stays consistent whether it arrives through the portal or by email.

Priority and SLA: how to set urgency

Priority and impact are two different questions, and keeping them separate is what stops every IT support request from being marked “urgent”. Priority is how soon an agent should work the ticket. Impact is how much the problem hurts the business. A cosmetic glitch reported by the CEO is high impact but low priority; a single blocked salesperson mid-deal may be high priority despite low headcount impact.

Set priority from the combination:

• Critical is reserved for a widespread outage or a fully blocked team with no workaround. Work starts immediately.
• High is a blocked individual or a degraded service that is slowing real work.
• Medium is a problem with a workaround, scheduled around higher tickets.
• Low is a request with no time pressure, such as a nice-to-have change or a question.

An SLA, or service level agreement, is the time commitment your desk attaches to each priority. A typical scheme is a one-hour first response and four-hour resolution target on Critical, four hours and one business day on High, and longer windows below that. The SLA is the clock; the priority is the order. Because this service request template captures priority and impact on every ticket, JSM has the values it needs to start the right SLA timer automatically the moment the ticket is created, instead of an agent setting it by hand later.

Ticket routing and assignment

Once a ticket is categorized and prioritized, routing decides who picks it up. The goal is for the right specialist to see the IT support request in their queue without a human triaging it first.

Routing keys off the Category field. With automation, a rule reads the category on creation and assigns accordingly: Network tickets to the network queue, Software tickets to the application owner, Account tickets to identity and access. The same rule can set the component, add a watcher, and notify the on-call specialist in Slack or email.

Three things make routing reliable on a help desk ticket template. Make Category required so automation always has a value to act on. Keep one owner per category so there is never ambiguity about who works a queue. And add a catch-all rule for anything uncategorized, so a malformed ticket lands somewhere a human will see it rather than disappearing. Built this way, the template removes the manual triage hop entirely: the requester picks a category, and the ticket arrives where it belongs.

Best practices

• Separate impact from priority. Priority is how soon you work it; impact is how much it hurts the business. Keeping them distinct prevents the “everything is critical” trap.
• Ask for exact error text, not paraphrases. “It said something about a server” cannot be searched in your knowledge base. “Error 0x80070005: Access is denied” can.
• Use variables for the parts that change. With variables in templates you can prompt the reporter for the device name or category at create time, so the template stays generic but every ticket comes out specific.
• Route automatically. Combine the Category dropdown with automation to assign the ticket and notify the right specialist the moment it is created.

A strong request versus a weak one

A weak request forces the agent to chase basics before any real work begins:

Summary: Computer not working Description: Please fix asap, very urgent!!!

There is no device, no error, no category and no sense of real impact, so it stalls in triage.

A strong request, built from this template, is actionable on first read:

Summary: Cannot connect to office Wi-Fi on MacBook Pro Category: Network Priority: High Impact: Single user blocked, working from a phone hotspot Affected systems: MacBook Pro M2 (asset tag #1284), Okta SSO Description: Wi-Fi drops every few minutes since Monday’s update. Error: “Authentication failed”. Steps already tried: Restarted the device, forgot and rejoined the network, switched to guest SSID.

The second ticket can be categorized, prioritized and routed without a single clarifying reply.

How to use this template in Jira

1. Install Process Templates for Jira from the Atlassian Marketplace. It is free for up to 10 users.
2. Build a Get IT Help request with these fields in any JSM service desk project, then save it as a template. See creating issue templates if you are doing this for the first time.
3. Add variables for the parts that change so the create screen prompts for category, device and priority. See variables in templates.
4. Launch IT support tickets from the template in one click with the screen prefilled and ready to submit.

Frequently asked questions

What should an IT support ticket template include? A strong IT support ticket template captures the requester’s contact details, a specific summary, a full description with exact error text, a category, a priority and a separate business impact, the affected systems, the steps to reproduce, the steps already tried, and any supporting attachments. Those fields let a service desk categorize, prioritize and route the ticket without a single clarifying reply.

What is the difference between priority and SLA on a support ticket? Priority is how soon agents work the ticket relative to everything else in the queue. An SLA is the time commitment attached to that priority, for example a four-hour first response on a High ticket. Priority sets the order, the SLA sets the clock, and a consistent service request template feeds both because every ticket carries the same priority and impact fields.

How does a help desk ticket template route tickets to the right team? Routing keys off the Category field. Pair the Category dropdown with Jira Automation so a Network ticket lands in the network queue and a Software ticket lands with the application owner, the moment it is created. Because the help desk ticket template asks for the category every time, automation always has a value to route on.

How do I create a reusable IT support request template in Jira? Install Process Templates for Jira, build a Get IT Help request in a Jira Service Management project with the fields on this page, save it as a template, then add variables for the parts that change such as category, device and priority so your team launches a consistent IT support request in one click.

Related templates

Pair the IT support request with the rest of your service desk: the Incident report template for outages, the Request for new software template for procurement, the VPN access request template for connectivity, and the change management template for standard IT changes. Or browse the full template library for matching formats across software, ITSM and support work.