A customer's account context, right in the ticket
Billing status and CRM history show up directly in the JSM request view, so an agent doesn't have to switch tools mid-ticket to find out who they're talking to.
Jira Service Management (JSM, formerly Jira Service Desk) is Atlassian's ITSM and helpdesk product, a different animal from standard Jira Software's dev-ticket tracking. It gives support teams queues, SLA tracking, a customer-facing portal, and request types built for incidents, changes, and service requests rather than engineering sprints.
Customers submit requests through a branded portal instead of emailing an inbox, and each request routes into a queue agents work from, with SLA timers tracking response and resolution deadlines automatically.
Request types define the fields and workflow a given kind of ticket follows, a password reset looks nothing like an incident report, and both can live in the same project with their own rules.
Higher tiers add approvals and formal change management, useful once IT requests need sign-off before anything happens.
An agent working a JSM queue sees exactly what's inside Jira: the request, its SLA clock, the conversation history. What they don't see without leaving the ticket is whether that customer's account is current on billing, or what their CRM history looks like.
And when a request resolves, that resolution just sits in Jira unless something's built to carry it back out, a CRM note, an invoice credit, a notification to a different team entirely.
Billing status and CRM history show up directly in the JSM request view, so an agent doesn't have to switch tools mid-ticket to find out who they're talking to.
When a request resolves, we can have that update the CRM, trigger an invoice credit, or notify whoever downstream actually needs to know, without an agent doing it by hand.
Tell us what they have to go check manually, and we'll bring it into the ticket.
Point us at what your agents have to go look up by hand for every ticket, and we'll have it show up automatically instead. JSM's one system in your support stack; if the real friction is somewhere else entirely, that's just as worth fixing.
Let's talk →Jira Service Management is Atlassian's ITSM and helpdesk product: a customer portal, request queues, SLA tracking, and workflows built for support, incident, and change management, distinct from Jira Software's software-development ticket tracking.
Same product, different name. Atlassian rebranded Jira Service Desk to Jira Service Management as it expanded beyond basic helpdesk functionality into broader ITSM features.
JSM is priced per agent per month, with tiers (Free, Standard, Premium, Enterprise) adding more automation, incident management, and advanced ITSM features as you go up. Check Atlassian's current pricing page, since tiers and numbers shift.
Yes, a branded self-service portal is a core part of JSM. Customers submit requests there instead of emailing an inbox, and can track status without an agent having to reply manually.