You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Jira Service Management is an end-to-end service management platform for IT teams and business teams handling service requests from customers or employees. Originally known as Jira Service Desk, Atlassian reintroduced the platform as Jira Service Management with multiple enhancements designed to benefit modern support teams in the post-2020 environment.
Customer satisfaction rides on the support team’s back, sometimes more than any other team. If a customer needs something, the support team has to make sure they get it. If something goes wrong, the support team has to make sure it’s resolved quickly. A good service desk, used in the right way, is essential for maintaining customer satisfaction.
This Jira Service Management guide explains what a good service desk, used in the right way, actually involves. And how your Jira Service Management system can turn your support team into customer service pros.
Originally, Jira Service Management was targeted solely at IT service management (ITSM) teams, who manage and maintain hardware and software for their customers, whether internal or external. Service desk software is used by those customers to request service by generating a ticket, e.g. “I need a new phone/laptop” or “I need a password reset” or “my system isn’t working properly”.
Over time, Atlassian realized that non-ITSM teams were starting to use service desks to provide services in an ITSM-like way. For example, a HR team might use one to onboard/offboard employees and handle requests from new starters. A facilities team might use one for building maintenance issues, desk moves, event planning, and requests for equipment. As a result, Atlassian have added features for business teams as well, such as project templates for facilities, legal, HR, and general service management. You could now say that Jira Service Management is more of an enterprise service management (ESM) tool than just an ITSM one.
The problem with many ITSM service desks is that they’re overengineered, incorporating most if not all of the 26 processes described in the IT Infrastructure Library (ITIL). This makes them too expensive and too complicated to use. Many of those processes just aren’t relevant to most companies.
Jira Service Management (JSM) keeps things simple for support teams by incorporating the four core ITIL processes only: request fulfillment, incident management, problem management, and change management. Because Atlassian knows that these are all most companies need.
Plus, JSM is an agile tool as well as being an ITSM tool. In the past these were two very different disciplines. The fact that JSM does not rigidly adhere to ITIL allows scope for features inspired by agile methodologies, such as agile incident management, cross-team collaborative capabilities, and improved reporting.
Many support teams use service-level agreements (SLAs) to ensure that they are delivering good service. However, a lot of traditional service desks make it difficult to configure, change, track, and report on SLAs.
Jira Service Management lets you create the SLAs you want in a matter of minutes. It’s much more flexible and comes with several out-of-the-box reports, along with the ability to create your own, so you can check how well you’re complying with your SLAs. After all, your SLAs are basically useless if you’re not tracking your performance against them.
In order for service desk teams to maintain customer satisfaction, they need to measure how well they’re doing and identify areas in which they could do better. Both of these things require looking at reports.
Jira Service Management comes with default reports, custom reports, and dashboards. The default reports can’t be changed. The custom reports can be edited and you can create your own. Jira dashboards let you add multiple reports (called gadgets) to a single page and offer the most dynamic kind of reporting.
Dashboards also allow you to enhance your JSM data visualization and data storytelling by adding Atlassian Marketplace apps like Custom Charts for Jira, which offer more control over chart type, data choices, color, descriptions, and labels.
There are 5 reports that we think support teams ought to be looking at, which either come with Jira Service Management or can be generated using Marketplace reporting apps.
Customer satisfaction report – this lets you see your customer satisfaction (CSAT) ratings in chart form. The single CSAT report that comes with native JSM is a simple table with limited filtering options, but the right Marketplace app will let you make different kinds of charts and filter the data however you want.
Created vs Resolved Issues – this shows whether support teams are keeping up with the work that’s coming in. It comes out of the box as a basic line chart, but you may want to make a more customized version using a Marketplace app.
Workload report – this helps see whether support agents are able to stay on stop of their workload, or may have too many issues to deal with. The native JSM pie chart does the job, but you may want to seek out a reporting app to customize the data and how it’s displayed, e.g. if you want to show/hide specific assignees or chart by original or remaining estimate instead of issue count.
Organizations report – this lets you see trends across your customer base, e.g. which companies are submitting the most tickets and what types of tickets they are. Most of the native reports don’t let you chart by Organization, so you’d need an app like Custom Charts for Jira to get insights into where your requests are coming from.
SLA reports – these let you see whether you’re meeting the expectations stipulated in your service-level agreements (SLAs). There are a few SLA reports that come with JSM by default, and you can create your own using the JSM custom reports option. However, your only charting option is a basic line chart. Marketplace reporting apps offer more options.
The JSM reports above are a good start, but identifying problems, trends, and areas for continuous improvement requires support teams to go deeper into their ITSM data.
For example, you might want to generate a chart that looks at issue priority and status per organization, SLAs breached vs not breached per assignee, and requests broken down by component. You might also want to look at average customer satisfaction (CSAT) rating per assignee, open ITSM issues, and changes planned for the month. (Many of these reports will be useful to non-IT support teams such as facilities teams as well.)
Out-of-the-box Jira Service Management doesn’t let you report on these data points, but there are some great reporting gadgets on the Atlassian Marketplace that do.
With out-of-the-box Jira Service Management, the only way to get SLA reports on a Jira dashboard is with the Service Project Report gadget. However, this gadget doesn’t let you make SLA reports on the dashboard. You have to go into the project and generate them as project reports first, then the gadget pulls these already made reports onto your dashboard.
It means, if you have multiple service projects, you have to generate each one on a per-project basis, and if you want to change the configuration, you have to go back into the project. You can’t do it on the dashboard. In effect, you lose the speed and efficiency that comes with dashboard reporting.
Ideally you need a Marketplace app that lets you build reports and charts out of your SLA data directly on the dashboard. Procuring an app for this purpose is simultaneously an opportunity to gain a lot more choice and control over how those charts appear.
The role of the support team is to maintain and increase customer satisfaction. As the main way to do this in Jira Service Management is by using reports, then reports based on your CSAT ratings must be your starting point. Analyzing the nature of requests and who’s submitting them; measuring your time to first response and resolution; and checking whether you’re keeping up with issues coming in, are all well and good. But none of these metrics are more important than knowing whether the customers are actually happy. The strange thing is, the CSAT survey in JSM often gets overlooked.
Support teams ticking all the right boxes might assume their customers are happy, but that doesn’t mean they are. For example, even if you’re resolving issues within the time stipulated in your SLAs, you might not be giving the customer what they want. You want to avoid the watermelon effect, in which good, ‘green’ metrics hide the true, ‘red’ state of your operation.
Basically, you want to always pay equally close attention to whether your customers are happy as to whether you’re hitting your other ITSM metrics. After all, a good service desk isn’t one that meets all its SLAs. It’s one that actually, and satisfactorily, solves the customers' problems.
Head of Content
Old Street Solutions