Try our new research platform with insights from 80,000+ expert users
JIRA Service Management Logo

JIRA Service Management pros and cons

Vendor: Atlassian
4.1 out of 5
Badge Leader
3,218 followers
Post review

Pros & Cons summary

Buyer's Guide

Get pricing advice, tips, use cases and valuable features from real users of this product.
Get the report

Prominent pros & cons

PROS

JIRA Service Management allows for customized workflows and processes, enhancing operational efficiency and adaptability.
It integrates seamlessly with other tools and platforms like Confluence and external third-party products, improving work coordination and project tracking.
The automation features streamline ticket handling and workflow, increasing productivity and reducing manual intervention.
Its compatibility with Agile and Kanban methodologies supports effective project and task management within development teams.
Customization capabilities enable users to modify the tool to meet specific organizational needs, including support for multiple languages and tailored feature access.

CONS

JIRA Service Management's SaaS version is not available for large organizations exceeding 2000 users, limiting scalability options.
JIRA lacks features for project management and requires marketplace add-ons for customer-facing systems.
Integration with non-Atlassian products is limited, and support lacks comprehensive installation guides for individual products.
Time tracking and workflow efficiency suffer due to the absence of built-in features for logging work type or sorting queued tickets by product.
Asset management, initial setup complexity, and performance in cloud service management present challenges for long-term usability and deployment.
 

JIRA Service Management Pros review quotes

MA
Apr 1, 2021
The links between the help desk and Jira issues and between Confluence and Jira issues are most valuable. I can write requirements in Confluence and link them to user stories in Jira and test cases. I can see my test coverage and all that kind of stuff. The integration between these three is very useful. It is pretty customizable, and it integrates well. There are a lot of add-ins and a lot of connectors to third-party products. In my last company, we used Test Royal for managing all the tests, and it integrated perfectly with that. For any issue or bug, we could see what tests have been run and the complete history of the tests.
YK
Sep 11, 2019
This is the most complete and versatile enterprise task management product and issue tracker.
JP
Dec 30, 2022
Jira Service Management has a workflow feature you can configure for your specific requirements. It also lets you efficiently manage service requests with team members.
Learn what your peers think about JIRA Service Management. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
816,636 professionals have used our research since 2012.
AbhishekSingh10 - PeerSpot reviewer
Sep 16, 2022
It scales well.
Andrew Burt - PeerSpot reviewer
Sep 28, 2022
One of the valuable features is that an automatic response or action can be taken on tickets.
Sai Durga - PeerSpot reviewer
Aug 1, 2022
The initial setup is pretty easy.
Joe Dede - PeerSpot reviewer
Dec 23, 2022
There are two things that I value very much about this product. One is the service levels management – the SLA agreement management part of it – and knowledge management.
ST
Jun 21, 2020
It's easy to set up the solution.
BR
Aug 5, 2021
Customizations are most valuable. The customization of workflows is the main power of the Atlassian tools in general.
Anna Virtsan - PeerSpot reviewer
Jul 26, 2023
It has improved our work in a number of ways. First, it has made everything much faster. Before Jira Service Management, it could take weeks to resolve a ticket.
 

JIRA Service Management Cons review quotes

MA
Apr 1, 2021
The way it handles subtasks can be improved. We would really like the ability to have different types of subtasks. If we have a user story for a feature, we would like to have a subtask for documentation, a subtask for requirements, a subtask for development, and a subtask for testing. Right now, we just make four subtasks, but there is no way to specify their type, so we have to add a custom field to specify what type of work is this. It just means you've got to look at more data. For logging time or time tracking, we would like to have something using which we can define the work type we're doing. We would like to log whether we're working on a bug, a new development, scope change, or rework. We've got a user story for which we do the dev, and then we have to do more dev. It is the same story, but some of it could have been a scope change, and some of it could be a rework because we either screwed up the first time or missed something obvious. Currently, we have to have a custom field and track that separately. It would be nice to have some kind of work type for logging time.
YK
Sep 11, 2019
Integration possibilities with other products that are not Atlassian would be helpful. Support should also provide separate installation guides for each product even though they are easy to install.
JP
Dec 30, 2022
What needs to be added in Jira Service Management is the user screen. You'll find it very weird if this is your first time using the solution. The user-friendliness of its interface needs improvement.
Learn what your peers think about JIRA Service Management. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
816,636 professionals have used our research since 2012.
AbhishekSingh10 - PeerSpot reviewer
Sep 16, 2022
The deployment can be a bit complex, especially for those who are not technical.
Andrew Burt - PeerSpot reviewer
Sep 28, 2022
A lot of users have said that they want a feature that was on the on-prem version of Jira and the vendor can't deliver. They're either unwilling or unable to give feature parity.
Sai Durga - PeerSpot reviewer
Aug 1, 2022
I'd like to update the dashboard so that more features are available.
Joe Dede - PeerSpot reviewer
Dec 23, 2022
The price is a point of contention for me. It does overall work out as a significant amount of money that will be spent over a shorter period of time.
ST
Jun 21, 2020
JSD has some analytics, but it's pretty much basic and simple dashboards. There's no mobile application for JSD. It really would benefit from better implementation with other vendors. We're heavily reliant on some external marketplace applications.
BR
Aug 5, 2021
Its UI is a bit overwhelming for new users. That has been the problem with Jira for a long time. If they could put some fields that we could use to simplify the UI, it would be good.
Anna Virtsan - PeerSpot reviewer
Jul 26, 2023
There is room for improvement in support.