
How to Set Up Jira Service Management for ITSM (2026 Guide)
To set up Jira Service Management (JSM) for ITSM, pick your plan first, then build in this order: create a service project from the IT Service Management template, set up request types and the portal, add queues and SLAs, then turn on incident, problem and change workflows. The plan matters most, because full change and problem management need Premium.
I have run several JSM rollouts. The template takes five minutes. The hours go into request types, agent permissions and plan limits. This guide follows Atlassian’s JSM pricing page and support docs, checked in October 2026.
Agents vs customers: how you pay
- Agents are the people who work tickets. You pay per agent.
- Customers are the people who raise requests. They are free and unlimited.
So the employee who emails IT never costs a seat. That makes JSM cheaper than tools that charge for everyone.
Plans at a glance
| Free | Standard | Premium | Enterprise | |
|---|---|---|---|---|
| Price per agent/month | $0 | $21.50 | $55.28 | Quote |
| Agents | Up to 3 | Up to 100,000 | Up to 100,000 | Up to 100,000 |
| Portal, queues, SLAs | Yes | Yes | Yes | Yes |
| Alerts and on-call | Yes | Yes | Yes | Yes |
| Automation steps | 1,250 per month total | 3,000 per user/month | 6,500 per user/month | 9,500 per user/month |
| Assets objects included | None | 5,000 | 50,000 | 500,000 |
| Change management with approvals and risk | No | No | Yes | Yes |
| Virtual service agent | No | No | Yes | Yes |

Above the included Assets allowance, objects start at $0.02 per object per month. Paying yearly saves up to 17%.
The big catch: In late 2024, Atlassian moved advanced incident, problem and change features to Premium and Enterprise. Free and Standard still get the basics: an incident category, incident queues, alerts and on-call schedules. But major incidents, post-incident reviews, the change calendar, automated change risk checks and problem management need Premium. Atlassian explains the split in its capabilities update note.
Real cost example: 10 agents on Standard is about $2,580 a year. On Premium, about $6,634. If you are buying JSM for ITIL-style change control, budget for Premium from the start.
Before you start
- Pick the plan using the table above. Rebuilding change workflows after a downgrade is painful.
- List the requests you will support on day one. Usually access requests, hardware, software and general IT help. Do not model everything.
- Decide who is an agent. That decides your bill.
Step 1: Create the ITSM project
- Open Projects > Create project.
- Choose Service management, then the IT Service Management template.
- Name it and pick a short key, like ITSD. The key shows in every ticket ID.
- Choose company-managed for ITSM at any real size. It keeps workflows and schemes the same across projects. Team-managed suits a single small team that wants its own settings.
- Create the project. The template adds default request types and queues.
You now have a working service desk. But shipping the defaults as-is is the most common mistake.
Step 2: Request types and the portal
Request types are what employees see in the portal.
- Go to Project settings > Request types.
- Delete anything you will not support. A short list beats a long one.
- Rename each type in plain words. Write “I need a new laptop,” not “Hardware provisioning.”
- Trim each form to the fields you truly need. Every extra required field pushes people back to email.
- Group types into portal groups so the help center reads like a menu.
- Add your name and logo under Portal settings.
- Under Channels, connect a support email. For the first few months, most requests will still come by email.
Step 3: Queues and SLAs
Queues decide what agents see. Start with four:
- Unassigned: new tickets nobody owns
- Assigned to me
- Waiting for customer
- About to breach: anything close to missing its SLA
SLAs track response and resolution times. They exist on every plan, including Free. Start with two goals: time to first response and time to resolution. Set targets by priority. A common start is 1 hour to first response for High, 8 business hours for Normal. Add a business-hours calendar, or nights and weekends will count against you.
Do not confuse your SLA goals with Atlassian’s 99.9% uptime guarantee on Premium. They are different things.
Step 4: Incident, problem and change
On Free and Standard, set up the incident category and queues, and connect alerts and on-call schedules.
On Premium:
- Go to Project settings > Features and turn on Change management and Problem management.
- Review the change workflow. Set approval steps to match who really signs off.
- Add approvals to change request types, so nothing moves without sign-off.
- Connect CI/CD tools like Bitbucket Pipelines, Jenkins or CircleCI for deployment gating.
- Link incidents to problems and changes as you work, so repeat issues are traceable.

Step 5: Automation and alerting
Good first rules:
- Auto-assign by request type
- When a customer replies, move the ticket back to “In progress”
- Alert the team lead when a ticket is 30 minutes from breaching
Watch your limits. Free gets 1,250 automation steps a month for the whole site. Standard gets 3,000 per user a month. A rule that fires on every comment can burn through Free’s allowance quickly.
Opsgenie users: Atlassian stopped selling Opsgenie in June 2025. It shuts down on April 5, 2027. Its on-call and alerting features now live in JSM. Plan your move well before that date.
What experienced admins do
- One owner for the config. JSM rewards a named admin. Without one, schemes drift.
- Five to eight request types at launch. Add more only when real tickets show the need.
- Knowledge base early. Link a Confluence space so the portal suggests articles before people raise tickets.
- Review SLAs after 30 days. Your first targets are guesses. Adjust them to real data.
New option for Asana customers: Asana Service Management went live on September 22, 2026, for employee requests on Asana Enterprise and Enterprise+. Unlike JSM, it is for internal staff only. Our Asana Service Management guide covers plans and AI Resolution billing.
When JSM is overkill
- A five-person startup with a few IT requests. A shared inbox or the Free plan is enough.
- You need change control but cannot pay Premium. Standard will frustrate you.
- The work is really product or engineering tasks. Use Jira or Linear, not a service desk.
Common questions
How much does Jira Service Management cost?
Free covers up to 3 agents. Standard is $21.50 per agent a month and Premium is $55.28. Enterprise is quote-based. Customers are free.
Which plan has change management?
Premium and Enterprise. Free and Standard get basic incident handling, alerts and on-call, but not the change calendar, risk checks or problem management.
Do customers need a license?
No. Customers who raise requests are free and unlimited. Only agents who work tickets need a paid seat.
Are SLAs included on the Free plan?
Yes. SLA goals for response and resolution work on every plan.
Company-managed or team-managed for ITSM?
Company-managed. It keeps incident and change workflows consistent across projects.
What happens to Opsgenie?
Atlassian ends Opsgenie on April 5, 2027. Its alerting and on-call features are now part of Jira Service Management.
Prices and limits checked on Atlassian’s pricing page and support docs on October 14, 2026. Vendors change plans; confirm before you buy.



