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

Cherwell Service Management vs JIRA Service Management 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

Cherwell Service Management
Ranking in Help Desk Software
28th
Ranking in IT Service Management (ITSM)
27th
Average Rating
7.2
Reviews Sentiment
7.1
Number of Reviews
6
Ranking in other categories
No ranking in other categories
JIRA Service Management
Ranking in Help Desk Software
2nd
Ranking in IT Service Management (ITSM)
2nd
Average Rating
8.2
Reviews Sentiment
6.8
Number of Reviews
88
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 Cherwell Service Management is 1.7%, up from 0.7% compared to the previous year. The mindshare of JIRA Service Management is 7.3%, down from 10.7% 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%
Cherwell Service Management1.7%
Other91.0%
IT Service Management (ITSM)
 

Featured Reviews

Thobile Moeketsi - PeerSpot reviewer
Senior Manager at Sasria SOC Ltd.
Having everything in one location has significantly improved our efficiency and reporting
We need to be on VPN in order to set up and access the solution, and that has created some challenges. Even though it uses our Windows login, we still have to be on VPN. The product should be able to log tickets directly from system to system. We haven't got there yet and I'm not sure it's possible but it would determine the product's capability to integrate with other systems.
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.

Quotes from Members

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

Pros

"Clear processes with transparent responsibilities led to more efficiencies within the teams."
"The dashboard is very useful to get a quick overview of current tasks."
"All our activities are carried out in the one place."
"Its integration features, orchestration features, and discovery tools are the most valuable. It is also pretty stable, and it can be as scalable as you want."
"The dashboard and the reporting functionality are the solution's most valuable features."
"The most valuable features are problem management and change management."
"JIRA Service Management provides real-time updates to all the stakeholders, and offers the opportunity to create customized communication and track services, enabling more precise real-time changes and a customized version."
"I find the Kanban chart where we put each story in to be the most valuable feature. We use the Kanban chart to revise the project every morning in our five-minute meeting."
"Great to be able to create customized forms."
"The visibility features are great."
"We can track, monitor, and get all the details we need from the end-user's point of view for any service request."
"JIRA SD also helps for much better feedback on the work being done. All colleagues can see what is happening."
"JIRA Service Management is a very user-friendly solution."
"The most valuable feature of JIRA Service Management is a plugin we are using for the front end for simple user forms."
 

Cons

"Access is only available if we're on VPN."
"Areas for improvement would be the service catalog and customer catalog, which is not very user-friendly. The shopping cart experience is also terrible - you submit and go straight to the cart, you can't continue shopping or see your overall cost."
"The stability, specifically in the on-premises deployment model, could be improved."
"Application service mapping, GRC, SecOps, and things like that need improvement."
"I would like to see the user interface changed, it is not very user-friendly, and it transitions workflows."
"JSM's ability to handle large volumes of emails isn't great."
"The product does not allow customization of reports."
"The initial setup is very complex."
"JIRA protects the end-user, but for the configuration, more rules could be added to improve the workflow."
"Currently lacks an asset management module that can affect deployment."
"I don't think the program is very scalable."
"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."
 

Pricing and Cost Advice

"For an ITIL user, the cost is probably about 50 bucks a month."
"It costs around $150 to $200 per user."
"It is a cheaply priced product."
"It is one of the premium products on the market, but it is very costly, especially in the Indian market."
"The license we use is on a yearly basis. As a Solution Partner, we were using the free one and were using the free plugins. We were also giving our own plugins to the Atlassian Solution Partners for free. We don't pay anything to Atlassian."
"I would rate the pricing a seven out of ten, where one is low price, and ten is high price. It's competitively priced."
"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."
"Right now, there are only two of us who are both agents on the help desk and developers. We might be on the free version because we're less than three agents or users. I'm looking at Zephyr tests, which have a $10 a month flat rate, so right now, it is $10 a month. There are lots of add-ons. They do a free version, a standard version, and a premium version. In the last company, we started on $50 a month. By the time I left, we were paying $4,500 a month. That was mainly because we had 100 users on Confluence. I bought an add-on for Jira software for which we had 10 users, and that was $5 per user per month. It was costing me $500 a month, whereas it should only be $50 a month. I don't know if licensing fee has changed. I'd like our whole company to use it, but the big problem is the licensing because the Confluence side is what is really useful, but if I add 30 users to Confluence and then buy an extension for Jira software, I've got to pay for 30 licenses, even though I've only got two users in Jira software. It is the one big disadvantage of cloud software. You always have to pay for the number of seats regardless of which product you are on. This will probably severely limit how many people would use it because I'm not going to start paying $10 per user per month for a Jira software add-on when there are only two people using it."
"It depends on the number of users but it starts at $20 per month per user. I would rate them a three out of five for pricing."
report
Use our free recommendation engine to learn which IT Service Management (ITSM) solutions are best for your needs.
883,692 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
15%
Manufacturing Company
12%
Energy/Utilities Company
11%
Healthcare Company
9%
Manufacturing Company
10%
Financial Services Firm
9%
Computer Software Company
9%
Educational Organization
7%
 

Company Size

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

Also Known As

No data available
JIRA Service Desk, Atlassian Jira Service Management
 

Overview

 

Sample Customers

Ausenco, Highlights for Children, B/E Aerospace
mgm technology partners, Telestream, Build.com, Zend Technologies, OfficeDrop, PGS Software, American Diabetes Association, NEPTUNE Canada
Find out what your peers are saying about Cherwell Service Management vs. JIRA Service Management and other solutions. Updated: March 2026.
883,692 professionals have used our research since 2012.