No more typing reviews! Try our Samantha, our new voice AI agent.

JIRA Service Management vs SolarWinds Service Desk comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 29, 2025

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
6.8
Number of Reviews
88
Ranking in other categories
Help Desk Software (2nd)
SolarWinds Service Desk
Ranking in IT Service Management (ITSM)
16th
Average Rating
9.0
Reviews Sentiment
6.5
Number of Reviews
3
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of March 2026, in the IT Service Management (ITSM) category, the mindshare of JIRA Service Management is 7.3%, down from 10.7% compared to the previous year. The mindshare of SolarWinds Service Desk is 0.8%, up from 0.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
IT Service Management (ITSM) Mindshare Distribution
ProductMindshare (%)
JIRA Service Management7.3%
SolarWinds Service Desk0.8%
Other91.9%
IT Service Management (ITSM)
 

Featured Reviews

Sohaib Ahmad - PeerSpot reviewer
Vice President Service Delivery at quixel
Comprehensive workflows and data views have supported complex teams but still need cost improvements
JIRA Service Management is costly. The pricing structure needs improvement. When I add some plugins, I have to pay the cost for every user whether they are using it or not. For smaller companies, the detailed workflow editing and the kind of details that JIRA Service Management provides would be complex. For startups and smaller companies, JIRA Service Management would be complex. The cloud offering is easier because I don't have to manage the infrastructure. There are two templates of the project: company-managed and team-managed. Team-managed is a newer feature, which is good for startup-kind companies where they don't need control over data from multiple projects displaying in one dashboard. For startups, JIRA Service Management is somewhat complex with its schemes and everything. Capacity management should be improved in terms of additional features in the next release of JIRA Service Management.
Vaibhav Patkar - PeerSpot reviewer
CISO at Orient Technologies Pvt. Ltd.
Improved service requests and network monitoring have increased efficiency but integration needs work
SolarWinds Service Desk is a recognized product across the world and a dependable product. Kaseya is somewhat dated, and SolarWinds Service Desk has better connectivity in terms of superior integration facilities compared to Kaseya. Additionally, SolarWinds Service Desk offers multiple options within the same tool, including ITSM as well as NOC and network monitoring capabilities. SolarWinds Service Desk has much greater acceptability in the market and a wide range of implementations and integrations with various tools and applications. Life becomes simpler when choosing a standard product, whereas Kaseya may not be as highly regarded in the market. SolarWinds Service Desk may have some flaws, but work is being done to address them. SolarWinds Service Desk is an affordable product. SolarWinds Service Desk is suitable for all customers ranging from small to enterprise. There are some small customers, and the primary usage is within the company itself, and then as customers require it, access can be provided to them.

Quotes from Members

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

Pros

"Easy to use and user-friendly."
"It's easy to set up the solution."
"The most valuable feature of JIRA Service Management is a plugin we are using for the front end for simple user forms."
"I believe that JIRA is one of the best project management tools."
"One of the best features is that I can share tickets with team members, at which point any team member is able to pick one up and work on it."
"Jira gets the basics right in terms of the Product Backlog and a Scrum Board that Scrum Teams can use to manage Sprint Backlogs."
"JIRA Service Management provides comprehensive data management, different views with customizable dashboards, a detailed level of customization from items to workflows to roles and teams, and very flexible integration through the Atlassian marketplace plugins."
"I like the history, the dimensioning, and how I can configure a space based on my preferences or the project circumstances."
"SolarWinds Service Desk is a recognized product across the world and a dependable product."
"The solution is very stable."
"What I appreciate the most about the product is that, as per the name given, it brings better visibility to the client in terms of their infrastructure, application, and performance."
 

Cons

"I feel that Atlassian isn't really interested in fixing everything because if they did, the partners that are developing the fixes and features would not have a place in the market."
"JIRA protects the end-user, but for the configuration, more rules could be added to improve the workflow."
"The search function could be improved. We have to search a certain way. There is no generic search; it is more object-oriented search."
"During the updates, when another version gets released, whatever I am tracking at that time gets lost and I have to type it all over again."
"Technical support is so-so. Some of them are good, some bad."
"With Jira, we were unable to implement time-based automation in its ticketing system."
"Field addition and removal features are not very intuitive in JIRA Service Management."
"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 primary concern so far is the integration part because of the APIs; this is the main area of concern."
"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

"We have an annual license with JIRA Service Management, but it is billed monthly."
"The pricing is very competitive and I think that it is okay."
"JSM's pricing is one of the best, starting at around $10 per user, per month, with volume discounts available."
"We may upgrade the license that we have. The license that we currently have is good for 500 agents, and it's not full yet."
"It is one of the premium products on the market, but it is very costly, especially in the Indian market."
"JIRA Service Desk has different pricing as it is based on agents. On average, the price is about $300 per agent."
"JIRA Service Management's pricing is pretty decent compared to competitors. I rate the pricing an eight to nine on a scale of one to ten."
"We have paid $20,000 recently for a one-year license for our on-prem server."
Information not available
report
Use our free recommendation engine to learn which IT Service Management (ITSM) solutions are best for your needs.
885,311 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
9%
Manufacturing Company
9%
Computer Software Company
8%
Educational Organization
7%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business30
Midsize Enterprise24
Large Enterprise33
No data available
 

Questions from the Community

What needs improvement with JIRA Service Management?
JIRA Service Management is costly. The pricing structure needs improvement. When I add some plugins, I have to pay the cost for every user whether they are using it or not. For smaller companies, t...
What needs improvement with SolarWinds Service Desk?
The primary concern so far is the integration part because of the APIs; this is the main area of concern. Currently, the installation of SolarWinds Service Desk is simple, but the integration may b...
What is your primary use case for SolarWinds Service Desk?
SolarWinds Service Desk is used for ITSM and network monitoring purposes. The major use cases being utilized are from Kaseya itself; the same use cases that were previously implemented are being re...
What advice do you have for others considering SolarWinds Service Desk?
I think the pricing of SolarWinds Hybrid Cloud Observability is now comparative and suited to our business model, which is the reason we have moved to that. It has actually helped my customers' tec...
 

Also Known As

JIRA Service Desk, Atlassian Jira Service Management
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 JIRA Service Management vs. SolarWinds Service Desk and other solutions. Updated: March 2026.
885,311 professionals have used our research since 2012.