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

HaloITSM vs JIRA Service Management comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Apr 5, 2026

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

HaloITSM
Ranking in IT Service Management (ITSM)
23rd
Average Rating
9.0
Reviews Sentiment
7.8
Number of Reviews
3
Ranking in other categories
No ranking in other categories
JIRA Service Management
Ranking in IT Service Management (ITSM)
2nd
Average Rating
8.2
Reviews Sentiment
6.8
Number of Reviews
90
Ranking in other categories
Help Desk Software (2nd)
 

Mindshare comparison

As of May 2026, in the IT Service Management (ITSM) category, the mindshare of HaloITSM is 1.9%, down from 3.2% compared to the previous year. The mindshare of JIRA Service Management is 6.9%, down from 9.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
IT Service Management (ITSM) Mindshare Distribution
ProductMindshare (%)
JIRA Service Management6.9%
HaloITSM1.9%
Other91.2%
IT Service Management (ITSM)
 

Featured Reviews

Abhilash Sherkane - PeerSpot reviewer
Practitioner - Service Management at Peristent Systems
An affordable and scalable solution that provides an excellent UI and many out-of-the-box integration capabilities
The product’s UI is very good. The tool’s performance is very good. The overall performance of the tool and the navigation is fast. It is very responsive. It has a lot of out-of-the-box integration capabilities with some of the common tools that we want to integrate. If something is not available out of the box, creating or configuring a new integration on HaloITSM is easier compared to other tools.
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

"The product’s UI is very good."
"The most valuable aspect is that is is codeless."
"The solution's initial setup process was quite straightforward... I rate the technical support a nine and a half out of ten."
"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."
"I think that people should really go for it because of its ease of use."
"Jira Service Management is flexible. It is easy to navigate without requiring extra learning. The user experience has been good."
"From where I sit, the cloud version is superior, mainly due to not having to manage the upkeep of Jira, which was quite frankly a pain, but that's just the nature of Jira."
"The customer portal with connection with our knowledge base has been most valuable."
"One of the main advantages of JIRA is that it can be customized for our solutions."
"This solution has helped us a great deal in project management tracking and forecasting."
"Two features I like about Jira are its ticketing system and its compatibility with Confluence. Also, the Knowledge Base is one of the more valuable features that would really benefit us."
 

Cons

"There are no improvements needed. There is very little that HALO has not already built that is not on its roadmap."
"The solution's integration part needs to improve...In the future release of the solution, I expect to see certain changes in the programming of the solution. A customer of the solution should be able to customize it as per their need."
"The product does not have its own orchestration engine."
"The solution should be more formalized. It could be more user-friendly."
"Field addition and removal features are not very intuitive in JIRA Service Management."
"I don't think the program is very scalable. It lacks scaling capabilities from the performance perspective and load balancing and some other infrastructure capabilities."
"The main issue with this solution is there's no limited subscription available for plugins we only use for a few people."
"While licensing is costly, setting up JIRA Service Management is overall good because the vendor helped me, and I also received support from JIRA support, making it a positive experience."
"The initial setup of JIRA Service Management can be complex for new users. There is a lot of configuration."
"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 reporting function of this solution, particularly the filters in the portal, could be improved."
 

Pricing and Cost Advice

"The solution's pricing model is good. Also, they still follow the old concurrent licensing method."
"The product’s pricing is competitive and less complicated."
"It's $69 per user per month. Only administrators need a license, and there is no limit to the number of endpoints."
"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."
"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."
"JIRA Service Desk has different pricing as it is based on agents. On average, the price is about $300 per agent."
"I would rate the pricing a seven out of ten, where one is low price, and ten is high price. It's competitively priced."
"We have paid $20,000 recently for a one-year license for our on-prem server."
"We have an annual license with JIRA Service Management, but it is billed monthly."
"I am using the free version, but my clients are paying for it. When they start, they evaluate it for 30 days, and after seeing the value, they move to its paid version."
"It's not really expensive, especially when you compare to ServiceNow or other solutions, and it's not expensive to maintain."
report
Use our free recommendation engine to learn which IT Service Management (ITSM) solutions are best for your needs.
896,099 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
University
12%
Government
10%
Healthcare Company
8%
Comms Service Provider
8%
Financial Services Firm
14%
Manufacturing Company
9%
Computer Software Company
7%
Educational Organization
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business30
Midsize Enterprise25
Large Enterprise34
 

Questions from the Community

Ask a question
Earn 20 points
What is your experience regarding pricing and costs for JIRA Service Management?
While licensing is costly, setting up JIRA Service Management is overall good because the vendor helped me, and I also received support from JIRA support, making it a positive experience.
What needs improvement with JIRA Service Management?
I feel JIRA Service Management could be better if the APIs from the sponsoring team provided more support and flexibility in API endpoints. Regarding JIRA Service Management's API and support, the ...
 

Also Known As

NetHelpDesk
JIRA Service Desk, Atlassian Jira Service Management
 

Overview

 

Sample Customers

Innocent Drinks, SKY TV, Sports Direct, Suzuki, Siemens, NHS, Cardiff City Council, Atos, AO.com, Ambitious about Autism, SEPA, York University etc.
mgm technology partners, Telestream, Build.com, Zend Technologies, OfficeDrop, PGS Software, American Diabetes Association, NEPTUNE Canada
Find out what your peers are saying about HaloITSM vs. JIRA Service Management and other solutions. Updated: April 2026.
896,099 professionals have used our research since 2012.