Try our new research platform with insights from 80,000+ expert users

JIRA Service Management vs SolarWinds Service Desk comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

JIRA Service Management
Ranking in IT Service Management (ITSM)
2nd
Average Rating
8.2
Reviews Sentiment
7.1
Number of Reviews
86
Ranking in other categories
Help Desk Software (2nd)
SolarWinds Service Desk
Ranking in IT Service Management (ITSM)
35th
Average Rating
9.0
Reviews Sentiment
8.4
Number of Reviews
1
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of July 2025, in the IT Service Management (ITSM) category, the mindshare of JIRA Service Management is 9.1%, down from 12.0% compared to the previous year. The mindshare of SolarWinds Service Desk is 0.6%, up from 0.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
IT Service Management (ITSM)
 

Featured Reviews

Karim Yousef - PeerSpot reviewer
Efficiently track and document projects with seamless tool integration
We are a management warehouse that provides services to different customers in different sectors. Primarily, we serve the banking sector and the military sector. We manage all the software delivery projects through tools such as JIRA Service Management or TFS Confluence is a great tool for…
BENDER BENEDICT - PeerSpot reviewer
A robust solution to automate and manage incidents and requests
The integration with other applications can use improvement because, for example, it was nearly impossible to integrate SolarWinds Service Desk with monday.com because we had to get an add-on from Zapier. The add-on allowed us to integrate with Jira Cloud Service, but we couldn't integrate completely and can only integrate with the project. I would also suggest that the incident and request management be separated on SolarWinds Service Desk. The solution's incident and request management feature are one of the core reasons why we had to migrate to Jira Service Management. It was difficult to filter incidents and requests. They are all compiled together in a single dashboard, which is not convenient for most of the users, especially the IT support person.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"Its integration is most valuable. It is pretty open for integration."
"The tool is scalable."
"The platform is easy to use."
"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."
"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."
"The product is not lacking anything that a QA will want to use."
"The centralized feature allows us to track test cases and integrate with automation and bug fixing."
"I'm mainly working in the ITSM module of JIRA Service Management, and the integration between the system incident and how you can link all the records to the change makes it quite powerful."
"The solution is very stable."
 

Cons

"The support we received was not fully provided at that time."
"It would be useful to be ale to link tickets across different gantt charts in Jira and Confluence."
"An AI feature that enables automation and alerts for users can be an improvement."
"In the Turkish market, the biggest problem is that they are looking for a server type of solution, but when it comes to Jira Service Management, Atlassian is a remote type of license. There are just two different options, data center and cloud."
"They need to work on the speed of Jira."
"It would be beneficial if we could turn comments into subtasks or other JIRA tickets directly."
"I would like to see the user interface changed, it is not very user-friendly, and it transitions workflows."
"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."
"The integration with other applications can use improvement because, for example, it was nearly impossible to integrate SolarWinds Service Desk with monday.com because we had to get an add-on from Zapier."
 

Pricing and Cost Advice

"Costs are about $50 per user per year. JIRA is sold in user tiers of 25, 50, 100, 250, 500, 2000, 10,000, and unlimited users. It is bad when you have 51 users then the price is based on that 100 user tier. Users at 100 will be the most cost effective."
"Jira Service Management has affordable license fees. It's $12 a month per person."
"Buying a software solution is only a half part of the solution (or even less). You need to optimize usage of the software by hiring professionals who will help you to make the most of the software, especially in the beginning."
"I price of JIRA Service Management is reasonable."
"Actually in Iran we don't have copyright or intellectual property, so we can use JIRA for free."
"JIRA Service Desk has different pricing as it is based on agents. On average, the price is about $300 per agent."
"For the people like us, the lower the price, the better. But when compared to other competitors, I think it's Jira's price is okay."
"This is pricey solution. Should we move to using all cloud solutions in our business, we may move to different tools that have multiple functionality versus having a solution for each area. This would be too pricey and we would need to replace Jira with a different solution that also offers other features."
Information not available
report
Use our free recommendation engine to learn which IT Service Management (ITSM) solutions are best for your needs.
860,592 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
19%
Financial Services Firm
10%
Manufacturing Company
8%
Government
6%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Also Known As

JIRA Service Desk
No data available
 

Overview

 

Sample Customers

mgm technology partners, Telestream, Build.com, Zend Technologies, OfficeDrop, PGS Software, American Diabetes Association, NEPTUNE Canada
Information Not Available
Find out what your peers are saying about ServiceNow, Atlassian, BMC and others in IT Service Management (ITSM). Updated: June 2025.
860,592 professionals have used our research since 2012.