Jira Service Management

What it is

Jira Service Management (JSM) is Atlassian’s service desk: request portal, queues, SLAs, incident and change management, and on-call, all built on the same work items as Jira Software. You can no longer buy it alone. Atlassian now sells it only inside the Service Collection, a single per-agent license that also includes Customer Service Management (CSM, an external-support app with its own help center and channels), Assets (an asset and configuration database), and an allowance of Rovo AI credits. Atlassian’s licensing page is explicit that the apps “can’t be bought separately”, and that the collection runs only on Atlassian Cloud.

The collection is a large business, not a side line. Atlassian’s Q3 FY26 shareholder letter said Service Collection had passed $1 billion in ARR. At Team ‘26 (5 to 7 May 2026) Atlassian added native voice AI, WhatsApp, and SMS to CSM, plus Rovo Service, an AI teammate for employee requests.

Where it fits

• Internal service desks where engineering already lives in Jira. IT, HR, facilities, and legal intake share one portal, and a request that turns out to be a bug links straight to an engineering work item without a sync tool. This is the use case JSM wins outright.
• Incident management after Opsgenie. Atlassian stopped selling Opsgenie on 4 June 2025 and ends support on 5 April 2027. JSM is the recommended home for incident management, and Compass for alerting and on-call. If you still run Opsgenie, the move is already on your calendar.
• External B2B support, with conditions. CSM gives you a separate customer help center, email, chat, and phone through an Amazon Connect integration, and the Rovo customer service agent answers first and hands off to humans. It fits when support escalates heavily into engineering. It is still younger than Zendesk for consumer-scale support: thinner macros, a smaller app ecosystem, and fewer workforce-management options.
• Agent access. The Atlassian Rovo MCP server now includes JSM tools for alerts, on-call schedules, and team lookups, with API-token authentication only (no OAuth yet). The REST API covers requests, queues, and Assets.

Pricing reality

Free covers up to 3 agents. On monthly billing, Atlassian listed Standard at $25 per agent and Premium at $57.30 for the first 15 agents when third-party trackers checked on 22 September 2026, with lower rates for each additional band (Standard $18.75 per agent for agents 16 to 100). On 13 October Standard and Premium list prices rose 7.5% and Enterprise 10%, which puts the entry rate near $27. Annual plans are priced by agent band: before the increase, 11 to 15 agents cost $3,750 a year on Standard and $8,600 on Premium. Enterprise starts at $168,500 a year for 201 to 300 agents. Portal customers who only raise requests do not need a license.

The usage meters matter more than the seats from 3 December 2026, when Atlassian starts billing them:

• CSM AI agent: $1.00 per resolution, billed from the first one, with no included allowance. Atlassian does not charge when the agent fails and escalates.
• Virtual service agent (Premium and Enterprise only): 1,000 assisted conversations a month included, then about $0.30 each.
• Rovo credits: 250, 700, or 1,500 per user a month by plan, pooled across the organization, then $0.01 per credit.
• Assets objects: 5,000, 50,000, or 500,000 included by plan.

Real numbers: a 12-agent internal IT desk on annual Standard pays about $4,030 a year after the increase. Point the same 12 agents at external support with the CSM AI agent closing 2,000 conversations a month, and the resolution meter adds $24,000 a year, six times the seat bill. That rate still undercuts Zendesk’s roughly $1.50 to $2.00 per automated resolution, and sits close to Intercom Fin’s $0.99.

Best for

IT, support, and ops leaders at 50 to 5,000-employee companies whose engineers already work in Jira, who need one service desk for IT, HR, and legal intake, and who want external B2B support escalations to land in the same system as the bug they trace back to.

Skip it if your support team handles high-volume consumer tickets and engineering is not on Jira. Zendesk or Intercom will be faster to run and deeper on support tooling.

Versus the alternatives

The largest players are ServiceNow in enterprise ITSM and Zendesk in customer support. Pick ServiceNow above roughly 5,000 employees, when you need one data model for IT, HR, and customer service cases and can fund a partner implementation. Pick Zendesk when external support is the job, ticket volume is in the thousands a day, and engineering escalation is the exception. Freshdesk is the lower-cost support desk to pick when you want to go live in weeks.

The fastest-growing entrants are Slack-native desks such as Unthread for internal requests, and AI-first agents such as Decagon and Sierra layered over an existing help desk. Rule: if most requests start as Slack threads and nobody audits the queue, test Unthread first. If you need an AI agent across several systems, not just Atlassian, price Decagon against $1 per resolution in CSM.

Watch-outs

• The resolution meter has no ceiling by default. At $1 per resolution from the first one, a busy external queue can cost more than the seats, and extra usage is switched on by default for most meters. Guard: before 3 December, set a usage limit per meter under Insights in Atlassian Administration, and model a month of expected AI resolutions at $1 before turning the agent on for every channel. A limit pauses the meter when it is hit, so size it above your normal peak.
• You pay for the whole bundle. Teams that only wanted an IT desk now pay for CSM, Assets, and Rovo inside the same seat, and the 13 October increase applies to all of it. Guard: count licensed agents carefully, because only agents need seats, and check at renewal whether a narrower desk such as Freshservice costs less for your agent count.
• Permissions are easy to get wrong. Capterra and G2 reviewers repeatedly call access setup confusing, and a misconfigured role can hide customers’ own requests from them in the portal. Guard: test the portal as a customer account from each organization before launch, and keep request-type permissions in a written matrix.
• Data Center has an end date. JSM Data Center reaches end of life on 28 March 2029, and the Service Collection itself is Cloud-only. Guard: if residency rules keep you on Data Center, confirm your Cloud data-residency region is available before you sign a multi-year renewal.