About JIRA Service Management

Formerly known as Jira Service Desk, Jira Service Management is an IT service management solution that unlocks high-velocity teams.

IT is in the midst of rapid transformation to build capabilities that enable quick delivery of great services while managing cost and risk. But old ways of working constrain progress. Rigid processes limit team agility. Disparate, disconnected tools interrupt the flow of information and hinder good decision-making. With Jira Service Management, teams can:

- Manage work across teams on one platform

- Enable employees and customers to quickly get the help they need with a self-service portal

- Respond, resolve and continuously learn from incident...


Read More

Supported Operating System(s):

Windows 7, Windows Vista, Windows XP, Mac OS, Web browser (OS agnostic), Windows 2000, Windows 8, Windows 10

262 Reviews of JIRA Service Management

Average User Ratings

Overall

4.36 / 5 stars

Ease-of-use

4.0

Value for money

4.0

Customer support

4.5

Functionality

4.5

Ratings Snapshot

5 stars

(137)

137

4 stars

(93)

93

3 stars

(23)

23

2 stars

(6)

6

1 stars

(3)

3

Likelihood to Recommend

Not likely

Very likely

Showing 1 - 5 of 262 results

April 2019

User Profile Picture

Josemaria from Maynilad Student Services

Verified Reviewer

Company Size: 51-200 employees

Industry: E-Learning

Time Used: Less than 6 months

Review Source: Capterra


Ease-of-use

5.0

Functionality

5.0

April 2019

From the Trusted Atlassian

In a crowded space for helpdesk apps, Jira Service Desk stood out because of the company that backs it up, its family of related apps and, the current integrations with existing third-party apps out there. Jira SD is well worth trying out.

Pros

From the same company of my favorite and trusted apps like Trello and Jira... We then gave Jira Service Desk a try. The user interface has a modern look and feel and is intuitive enough even for a novice user or admin. It has a pretty standard set of tools to run your usual IT Helpdesk and Support roles straight out of the box (Incident management, Problem, Change, SLA management, etc.). In fact, you can set up your helpdesk well within an hour (of course not counting the per company nitty-gritty). Default setup works, but it's also super customizable based on your company needs. The Dashboard has all the at-a-glance metrics, statistics and graphs to keep you up to speed with the overall status. Again, coming from Atlassian, it has a ton of possibilities in terms of integration with other apps. I feel the constant stream of dev improvements and updates.

Cons

Even though I mentioned that the third party apps can be easily integrable, we find the documentation for creating one's own integration apps a bit lacking. Also, the creation of tickets can be more streamlined or simplified (perhaps with the minimum number of fields and button clicks) to make it easier or faster to create and then further details can follow.

November 2020

Anonymous

Verified Reviewer

Company Size: 501-1,000 employees

Time Used: More than 2 years

Review Source: Capterra


Ease-of-use

2.0

Value for money

5.0

Customer support

5.0

Functionality

5.0

November 2020

Powerful and Capable, but easy to over complicate things

Initial setup can be complex but it can also be super powerful if you are able to configure it properly. It's visual scripting and workflow tool is really capable and easy to learn

Pros

Its flexibility. It's a simple statement, I agree, and you're probably reading this wondering why I'm being so vague. But JIRA software is a bit hard to summarize simply because it's just so flexible. There's no "correct" way to use it. It's rest API is pretty powerful too and very easy to extend Jira to "integrate" with 3rd party applications that doesn't have an official Jira integration.

Cons

Creating workflows can easily become very confusing and you can easily break how your projects in Jira work if you aren't careful. With every Jira production license you also get a free dev license so that you can set up an isolated dev/staging environment. This is invaluable and highly recommended. The downside is that there is no easy way to migrate any of your changes from dev to production. But there are 3rd party plugins for that.

Reasons for Choosing JIRA Service Management

Jira's popularity amongst many start ups and organizations said to me that it would be easy to find information from other uses on how to make Jira perform tasks that could be considered edge cases.

Reasons for Switching to JIRA Service Management

Lansweeper is great for asset management but its ticketing/help desk features are really lacking.

January 2021

Thomas from Information Technology and Services

Company Size: 201-500 employees

Industry: Financial Services

Time Used: Less than 2 years

Review Source


Ease-of-use

2.0

Value for money

3.0

Customer support

1.0

Functionality

2.0

January 2021

Do all - do nothing

Do you want a tool that does 1000 tasks but all of those tasks are 10% of what you need? GET THIS TOOL. Do you want a tool that has a million different customizations, yet none are what you want and everything is wrongly done? Get it ! Sure it's """cheap""" but with all the time you loose, not worth it. BTW, that 24/7 support, yeah, no, does not exist.

Pros

Well here's a tool that does everything, SD, incidents, KB, alerts, yes, it does a bit or everything.

Cons

It's awfull at doing things good. The new projects are barely compatible with new solutions, incidents and request are not configured correctly and can hardly be put in the same ticketing catalog. No advanced roadmaps (premium feature) in next gen projects. Automations are bad, tickets custom fields are sometimes not uderstood by the automation.

Reasons for Choosing JIRA Service Management

I didn't it was already set upon arival, but please, run away from it !

July 2019

Anonymous

Verified Reviewer

Company Size: 501-1,000 employees

Time Used: Less than 12 months

Review Source: Capterra


Ease-of-use

5.0

Functionality

4.0

July 2019

A great option for on-site ICT service desk management

Overall we are very happy with Jira Service Desk; it has allowed us to provide a higher level of support to users than our previous service desk, and non-profit pricing was very beneficial for us. The software is usable in its default setup but we have found that there is still plenty of customisation that can be done if needed to suit more complex requirements.

Pros

I find the UI of Jira Service Desk very clean and modern compared to other service desks software on the market. Included with the service desk is a customisable user-facing portal for users to raise tickets in, which proved very popular with staff when raising tickets alongside traditional email tickets. Due to the way Jira splits service desks into different projects, we were able to create service desks for other departments in the organisation which helped improve productivity and workflow. There are some very useful and well-designed default reports included for ticket statistics (which can be used to keep management happy!). We found the default setup of Jira Service Desk fit our needs very well, but it is very easy to customise ticket workflows and other features to suit more complex needs.

Cons

For a service desk technician using Jira Service Desk the back-end UI for managing tickets can be a little overwhelming, however this can be fixed by editing the default workflows for tickets to hide not required information and details. The administration settings are somewhat unintuitively set out for system administrators, but once you get to grips with the layout it becomes easy enough to find what you need from the settings page. We found the instructions on the Atlassian website for setting up an external redirect with a custom URL in IIS a little sparse on detail, but a quick trip to the Atlassian forums cleared up any queries we had with the process.

Reasons for Choosing JIRA Service Management

We chose Jira Service Desk as it was one of the few with a pricing model that worked for us; being a non-profit organisation, their free licencing for non-profits was a huge selling point to us. This was coupled with the fact we were at the time considering implementing both OpsGenie and Confluence (which are also Atlassian products) so we felt staying within the Atlassian ecosystem would prove beneficial.

Reasons for Switching to JIRA Service Management

We switched as part of a service contract change which meant our Kaseya service desk which was provided by our MSP was no longer an option. Instead we decided to look at alternative service desk software that could be used for our needs, and as we were at the time considering implementing both OpsGenie and Confluence (which are also Atlassian products) we decided to remain in the Atlassian ecosystem and choose Jira Service Desk.

February 2020

Chirag from Risk Administration Services

Company Size: 51-200 employees

Industry: Insurance

Time Used: Less than 2 years

Review Source: Capterra


Ease-of-use

5.0

Value for money

5.0

Customer support

3.0

Functionality

5.0

February 2020

Efficient service desk for companies small, medium or large

Prior to using Jira Service Desk, were using a combination of Excel and SharePoint with workflows. We couldn't get great reports. It was hard to customize. Workflows broke without a reason because, you know, it's SharePoint. And the entire process of serving customers was dead slow. We brought in Jira Service Desk as a test bed. Within 2 hours, we were testing and customers were putting in tickets. While we used most of the default settings, the value we were generating was way beyond we ever had. Then, we set up SLAs and watch reports for a few days. We were able to see everything we wanted - who reported the issue, when, what was the priority, how many comment exchanges happened, how much time did we spend, did we meet SLAs, what was the solution, etc. Fast forward 2 years. We are now able to create strategies to service internal and external customers better based on the data from Jira. It has helped us go from making gut-feel decisioning to data-centric decisioning. Good data wins debates. Jira helped us with good data. We are also utilizing Jira's excellent searching, dashboarding and API functionality to feed data to other systems and drive changes beyond just customers.

Pros

Jira Service Desk was very easy to get started with. You could literally sign up for it and begin using it within an hour. Ticketing system is very customizable and powerful. Customers can be added in bulk and customers can sign up for entering issues. We were able to create different projects (or service queues) so that customers could send requests for IT help, or administrative help, or help with projects. Each such project/queue had different fields. Metrics are all built into the software, so we can know how often Service Level Agreements were breached, who breached them etc. The sheer amount of customizability is a joy. However, without discipline and thoughtfulness, it is very easy to customize it the wrong way.

Cons

We feel that the price point could be lower and the speed could be a little faster. Atlassian has made improvements with speed. If a company had 5 people manning different queues and the issue volume is low, the cost would be ~1500/year for those 5 users. So, it would may not be cost effective for a small company that is watching their costs closely. We also felt that a Wiki is not built in. So, if a common solution needs to documented that spans multiple tickets, there's no way to do so. We could buy Confluence from Atlassian for an additional cost.

Reasons for Choosing JIRA Service Management

Asana has been working on improving the speed of their software. Their slowness has been well documented on various sites. Even their own team acknowledged and worked hard. We were not just read to jump into Asana due to the slowness. Trello was great - fast and easy to use. Reporting was missing. Pivotal Tracker felt like it was well suited for dev work and was comparable more to Jira Software. Basecamp felt like it was well suited for project work. Jira Service Desk fit the bill for IT help desk, admin help desk etc.

Reasons for Switching to JIRA Service Management

Our previous solution was built on SharePoint. It was slow. Very slow. We had workflows that drove communication after an issue was entered. Workflows would break often with hard-to-understand errors and debugging them was difficult. We had to build all the reports surrounding data we collected from SharePoint. Most reporting surrounding SharePoint were manual. We spent more time debugging issues with SharePoint than the time we spent on the most demanding customer. Something had to change. We tested Jira Service Desk one day and within hours our customers were using it. There was a day and night difference between the two systems and customers were happy. Built in reports were excellent.