Jira Service Desk Is Now Jira Service Management: Set It Up in the Right Order
Searching for Jira Service Desk? It's the same product. Atlassian renamed it Jira Service Management (JSM) in 2020 and kept adding to it. It's still Atlassian's help desk: a portal where people ask for help, queues where agents work the requests, and SLA clocks on every one. Here's what changed, what you pay for, and a setup order that avoids redoing work later.
It's the same product under a newer name. Older Jira Service Desk guides still hold for the basics: portal, request types, queues and SLAs.
Who needs a license: agents, the people who work requests. Customers who raise requests through the portal or by email don't.
Pricing: per agent per month. There's a Free plan for up to three agents, then Standard, Premium and Enterprise.
How Atlassian sells it now: as part of its Service Collection, alongside Customer Service Management and Assets.
Not the same as Jira: Jira tracks the team's own work in sprints. JSM handles requests from people outside the team, with service levels attached.
Standing up a Jira service desk, step by step
Done in this order, each step builds on the last and nothing needs rebuilding once customers arrive.
- 1
Choose the template that matches who is asking
IT service management suits an internal IT team handling incidents, changes and problems. The general service, HR and facilities templates suit other internal teams. For support aimed at outside customers, compare JSM with Atlassian's Customer Service Management before you commit.
- 2
Write request types in the requester's words
"Reset my password" and "My laptop won't start" beat "Access" and "Hardware". Each request type gets its own form fields and workflow, and the portal shows them as a menu.
Watch for: a long flat list. Group request types so people find theirs in a few seconds.
- 3
Decide who can raise requests
Either anyone with the link, or only customers you add. Group customers into organizations by company so agents see who belongs together and customers can see their colleagues' requests if you allow it.
- 4
Connect the email channel
Link a support address so emails turn into requests automatically, for the people who'll never open a portal.
Watch for: auto-replies. An out-of-office answering your confirmation email can open a fresh request each time.
- 5
Set SLA goals and calendars
Start with time to first response and time to resolution, measured against a calendar with your working hours and holidays.
Watch for: the clock while you wait on the customer. Pause it in that status, or agents get blamed for the customer's silence.
- 6
Build the queues agents work from
Unassigned requests, requests close to breaching their SLA, and high priority first. A queue is a saved filter, so keep each one short enough to clear.
- 7
Link a knowledge base
Connect a Confluence space so the portal suggests articles while someone types, and agents can share a page instead of retyping the answer.
Settle these before you invite requesters in
The first three shape the portal. The last two decide whether agents can actually finish a request inside JSM.
Which request type will a confused requester pick?
Vague names send people to the wrong form, and agents then rewrite requests by hand.
Which SLA clock stops while you wait for a reply?
Without a pause, response times look worse than the service really is.
Which requests need an approval first?
Access, purchases and changes usually do. JSM can route an approval before work starts, but someone has to name the approvers.
What does an agent need to see that isn't in Jira?
Plan, balance, contract end date, account owner. If that lives in your billing system or CRM, every request starts with a trip to another tab.
What has to happen somewhere else once a request is resolved?
A service credit, a note on the CRM record, a heads-up to the account manager. JSM closes the request. It doesn't do those for you.
What a JSM request still leaves out
A request in JSM knows the requester, the conversation, the SLA clock and anything you've linked from Assets. It doesn't know that the customer's last invoice bounced, that their contract renews next week, or that sales has an open deal with them. That lives in Stripe, QuickBooks, HubSpot or Salesforce, and the agent goes to look.
Assets can hold customer and contract records, and imports exist, but a one-off CSV goes stale within a month. Marketplace apps cover some CRMs, so check whether one shows the fields you need before paying for anything custom.
Where they don't, n-frames builds the feed that keeps each customer's billing and CRM details current on the request, and the path back out: a resolution that posts the credit in billing, writes the outcome on the CRM record and tells the account manager, with no agent copying it across.
Questions people ask
What is Jira Service Management?
It's Atlassian's service desk and IT service management product: a customer portal, request types, agent queues, SLA tracking, approvals and workflows for incidents, changes and service requests. It's separate from Jira, which tracks a team's own work.
Is JSM different from Jira Service Desk?
No, it's the same product under a newer name. Atlassian renamed Jira Service Desk to Jira Service Management in 2020 as it added IT service management features such as incident, problem and change management.
How much does Jira Service Management cost?
It's priced per agent per month. Free covers up to three agents, and Standard, Premium and Enterprise add more automation, incident management and admin features. Atlassian's pricing page has current figures, which depend on agent count and billing cycle.
Does JSM include a customer portal?
Yes. Every service space gets a portal where people pick a request type, fill in the form and follow progress, and it can suggest knowledge base articles before they submit.
Do customers need a Jira license to use the service desk?
They don't. People raising requests through the portal or by email are customers, and they don't use paid licenses. Only agents who work the requests do.
Can JSM show billing or CRM data on a request?
Not by default. Some marketplace apps bring in CRM details, and Assets can hold customer records you import. For live billing status and CRM history on every request, n-frames builds the connection from your billing system and CRM into JSM and keeps it current.