Methodology: built from Atlassian pricing pages, product docs, knowledge base articles and announcements, plus G2 review data, all checked on 7 Oct 2026. No vendor reviewed or paid for this article. We did not run hands-on tests.
Jira Service Management is Atlassian's service desk and IT service management (ITSM) app. It gives IT and business teams a request portal, queues, SLAs, and incident, problem and change workflows on the same platform as Jira. Since October 2025 it is sold inside Atlassian Service Collection, alongside Customer Service Management, Assets and Rovo.
If you are an IT lead checking whether Jira Service Management fits, this guide covers how it works, how it differs from Jira, what each plan includes, and what breaks when data moves into or out of it.
Key takeaways
- Jira Service Management is "the next generation of Jira Service Desk" (Atlassian announcement, 9 Nov 2020).
- It is sold only inside Service Collection: Free for up to 3 agents, Standard $20 and Premium $51.42 per agent per month, Enterprise by quote (Service Collection pricing page, as of 7 Oct 2026).
- Problem and change management are in Premium and Enterprise only (Service Collection pricing page, as of 7 Oct 2026).
- Jira is priced per user; Jira Service Management per agent, with unlimited customers on paid plans (Atlassian pricing pages, as of 7 Oct 2026).
- In a migration, CSV-imported comments become public in service spaces and SLA history does not carry over cleanly (Atlassian support docs, as of 7 Oct 2026).
What is Jira Service Management?
Jira Service Management (JSM) is Atlassian's cloud service management app for receiving, tracking and resolving requests from employees and customers. Agents work requests in queues against SLA goals, while requesters use a self-service portal. It covers request, incident, problem, change, asset and knowledge management for IT, operations and business teams.
"Jira Service Desk" is the product's old name (Atlassian announcement, 9 Nov 2020).
How Jira Service Management works
JSM runs on the Jira platform. Its unit of setup is the service space (older docs: "service project"), and each request is a work item (older docs: "issue").
Request types and the portal
Customers see request types, the portal forms such as "Get IT Help", and each one maps to an underlying work type. A new service space ships with five work types (IT Help, Purchase, Change, Fault and Access) and two default request types (Atlassian default configuration docs, as of 7 Oct 2026). Request types exist only in JSM spaces.
Queues, SLAs and workflows
Agents work from queues, saved views that sort incoming requests for triage. Each request follows a workflow; the default has four statuses: Waiting for Triage, Waiting for Support, Waiting for Customer and Resolved (Atlassian default configuration docs, as of 7 Oct 2026). SLAs are time goals such as time to first response or time to resolution. JSM calculates them from each work item's history, which matters in a migration.
Where Service Collection fits
Atlassian launched Service Collection on 7 Oct 2025 (Atlassian blog). It bundles Jira Service Management, Customer Service Management for external support, Assets for services and configuration items, and Rovo AI agents. It "is sold as a single offering", "the apps cannot be purchased separately", and it is cloud only. Existing JSM customers keep their configurations (Atlassian Service Collection licensing page, as of 7 Oct 2026).
Jira Service Management vs Jira
Jira (which absorbed Jira Software and Jira Work Management, per Atlassian's 1 May 2024 announcement) is for planning and tracking team work. Use Jira to plan and build work, and Jira Service Management to receive and resolve requests against SLAs.
| Jira | Jira Service Management | |
|---|---|---|
| Built for | Planning and tracking team work | Taking in and resolving requests from employees and customers |
| Who pays | Every user | Agents; customers are unlimited on paid plans |
| Free plan | Up to 10 users | Up to 3 agents |
| Intake | Team members create work items | Requesters use a portal and request types |
| SLAs and queues | Not in a standard Jira space | Built into every service space |
| ITSM practices | None out of the box | Incident and request; problem and change on Premium and above |
| Automation steps, Standard | 400 per user per month | 3,000 per user per month |
| Rovo credits, Standard | 25 per user per month | 250 per user per month |
Sources: Atlassian Jira Cloud plans docs, Service Collection pricing page, automation usage docs and Rovo usage limits, as of 7 Oct 2026.
Many teams run both: developers plan fixes in Jira while agents handle the linked requests. Atlassian's Data Center FAQ says Jira users without a JSM license can help through a limited unlicensed view; check the Cloud rules before you count seats.
Key Jira Service Management features
Atlassian's features page groups JSM into request, incident, problem, change, asset, configuration and knowledge management. Beyond the request basics above:
- Incident management. Alerting and on-call now live in JSM. Atlassian ended Opsgenie sales on 4 Jun 2025 and shuts it down on 5 Apr 2027 (Atlassian Opsgenie page, as of 7 Oct 2026). Major incidents and post-incident reviews are Premium and Enterprise features (Atlassian blog, 29 Oct 2024).
- Problem management. Group incidents under a problem, find root cause, record workarounds.
- Change management. Change requests, a change calendar, approvals by change type and automated risk assessment.
- Knowledge management. The knowledge base is Confluence: you link Confluence spaces or folders to a service space so portal users can find articles (Atlassian JSM docs).
- Assets. Atlassian's asset and configuration data store. Objects link to work items through an Assets object field.
- Automation and Rovo. No-code rules metered in steps and AI agents metered in credits. Extra usage is billed from 3 Dec 2026: $0.50 per 1,000 steps and $0.01 per credit (Atlassian automation and Rovo docs, as of 7 Oct 2026).
Jira Service Management plans and what's gated
Plan choice decides whether you get problem and change management at all.
| Plan | Price per agent/month | Problem and change | Assets objects included | Automation steps | Rovo credits per user/month |
|---|---|---|---|---|---|
| Free | $0, up to 3 agents | No | Not listed | 1,250 per subscription | Not listed |
| Standard | $20 | No | 5,000 | 3,000 per user | 250 |
| Premium | $51.42 | Yes | 50,000 | 6,500 per user | 700 |
| Enterprise | Contact sales (annual only) | Yes | 500,000 | 9,500 per user | 1,500 |
Source: Atlassian Service Collection pricing page, as of 7 Oct 2026. Paid plans go up to 100,000 agents; Assets overage is from $0.02 per object per month.
Two cautions. First, Assets gating is inconsistent across Atlassian pages: the pricing page lists Assets objects on Standard, while the migration assistant guide for Assets says Assets is "included with Premium and Enterprise plans" (Atlassian migration docs, as of 7 Oct 2026). Confirm with Atlassian if Assets drives your plan choice.
Second, new cloud list prices apply to renewals on or after 13 Oct 2026. Atlassian's example shows Service Collection Standard for 100 agents, billed annually, going from $19,700 to $21,000 (Atlassian future pricing pages, as of 7 Oct 2026). Partners Eficode and Valiantys both put the change at 7.5% for Standard and Premium and 10% for Enterprise (partner blogs, as of 7 Oct 2026), while Atlassian's example works out to about 6.6%. Check your own quote.
Common problems teams hit with Jira Service Management
JSM rates 4.3 out of 5 from 986 reviews on G2. On G2's comparison pages it scores 8.3 for ease of use and 8.0 for ease of setup and admin, against 8.8 for meets requirements (G2, as of 7 Oct 2026). It does the job, but takes configuration.
- Setup depth. Request types, work types, workflows and SLAs are separate layers that must change together.
- Plan surprises. Teams that start on Standard find problem and change management need Premium.
- Guardrails. Jira Cloud caps fields at 700 and work types at 150 per space, and priorities at 100 per space from September 2026 (Atlassian data limits docs, as of 7 Oct 2026). Heavily customized sites hit these.
- SLA edits are global. Changing an SLA configuration recalculates SLAs on all open work items (Atlassian KB, updated 25 Jun 2026).
- Backups are partial. Jira Cloud site backups exclude automation flows, Opsgenie-powered features such as on-call schedules, Assets and third-party app data (Atlassian backup docs, as of 7 Oct 2026).
Jira Service Management in a migration: what moves cleanly, what breaks
JSM migrations run Data Center to Cloud, from another tool into JSM, or out of JSM. The first has a deadline: Atlassian stopped selling Data Center to new customers after 30 Mar 2026, lets existing customers buy and expand until 30 Mar 2028, and makes Data Center, JSM included, read-only on 28 Mar 2029 (Atlassian Data Center end of life page, as of 7 Oct 2026).
The rule in every direction: records move, configuration is rebuilt. Workflows, automation rules, SLA definitions and running SLA timers are rebuilt on the target.
| Route | Moves cleanly | Rebuilt or re-checked | At risk |
|---|---|---|---|
| Data Center to Cloud (Jira Cloud Migration Assistant) | Request types, queues, SLAs, customers, organizations, portal settings | Automation flows (arrive disabled), workflow functions | Canned responses, mail handlers, issue collectors, linked KB articles (not migrated) |
| Into JSM by CSV | Work items, about 1,500 per file recommended | Statuses must already exist; request types set by ID, not name | Comments become public; SLAs keep counting on imported closed items |
| Assets | Objects and attributes by CSV, JSON or API | Import referenced types first; map references by label, since keys regenerate | Max 20 objects per field per work item; archived objects arrive active |
| Out of JSM | Work items by CSV, up to 10,000 per export | Copy elapsed SLA time into a field first | Assets and automation are not in site backups |
Sources: Atlassian migration, CSV import and export docs and KB articles, as of 7 Oct 2026.
The Jira Cloud Migration Assistant is built only for "migrations from Server or Data Center to Cloud" (Atlassian docs, as of 7 Oct 2026). Other moves use CSV, JSON or the APIs. What breaks most often:
- Comments go public. When CSV comments map to the Comments body field in a service space, "all the comments from your import file will become public" (Jira Cloud CSV import docs, as of 7 Oct 2026). Internal notes need another route.
- SLA history. CSV-imported items have only a creation event, so imported closed items keep counting. Atlassian's fixes: exclude them from SLA goals with a flag field, or bulk-transition them to Done (Atlassian KB, as of 7 Oct 2026). Original SLA results are lost either way.
- Automation. All flows moved by the migration assistant are disabled in Cloud by default, global flows need the "all flows" option, and Automation for Jira must be 7.2.6 or later (Atlassian migration docs, as of 7 Oct 2026).
- Duplicate accounts. A licensed Data Center user who already has a cloud customer account ends up with two accounts (Atlassian migration docs, as of 7 Oct 2026).
MigrateX runs these migrations as a controlled change: mapped, test-migrated, cut over with delta sync and reconciled.
Jira Service Management checklist
- List the ITSM practices you run. If problem or change is on it, budget for Premium.
- Confirm Assets plan gating with Atlassian if you track CIs.
- Count agents, not requesters.
- Check your renewal date against the 13 Oct 2026 price change.
- Estimate automation steps and Rovo credits before 3 Dec 2026.
- Map request types to work types before importing anything.
- Decide how internal notes will move, since CSV comments arrive public.
- Choose an SLA history approach: exclude imported items or bulk-transition them.
- Import referenced Assets object types first and map references by label.
- Inventory automation rules and plan to rebuild or re-enable each one.
- On Data Center, plan back from 28 Mar 2029.
FAQ
Methodology
We built this guide from Atlassian's pricing and licensing pages, Jira and JSM Cloud documentation, migration and knowledge base articles, and announcements, plus G2 data. All figures were checked on 7 Oct 2026 and name their source in the text. Partner figures are attributed and kept to body text. We did not run hands-on tests.
Disclosure: MigrateX, the publisher of this article, runs ITSM data migrations, including between platforms named here. No vendor reviewed or paid for this article.