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

HaloITSM 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

HaloITSM
Ranking in IT Service Management (ITSM)
21st
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
88
Ranking in other categories
Help Desk Software (2nd)
 

Mindshare comparison

As of February 2026, in the IT Service Management (ITSM) category, the mindshare of HaloITSM is 2.3%, down from 2.4% compared to the previous year. The mindshare of JIRA Service Management is 7.3%, down from 11.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
IT Service Management (ITSM) Market Share Distribution
ProductMarket Share (%)
JIRA Service Management7.3%
HaloITSM2.3%
Other90.4%
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 solution's initial setup process was quite straightforward... I rate the technical support a nine and a half out of ten."
"The product’s UI is very good."
"The most valuable aspect is that is is codeless."
"The initial setup is easy and straightforward."
"This is a flexible tool for logging and tracking issues efficiently."
"Some of the most valuable features are simplicity, ease of configuration, and ease of customization."
"The platform is easy to use."
"This service management solution has a good user interface. It helps improve your IT request requirements and makes tracking requests easier."
"The initial setup is pretty easy."
"It makes the IT department more transparent and helps the employees."
"The query language and the ability to create views of the data are very useful."
 

Cons

"There are no improvements needed. There is very little that HALO has not already built that is not on its roadmap."
"The product does not have its own orchestration engine."
"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."
"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."
"This solution lacks features for project management."
"JIRA Service Management could improve the forms. When you complete the form for the ticket, for example, to have more information given to the team. If they needed this information, you can give it to them. They need to add additional information for a better understanding of the whole picture of the issue or problem."
"JSM's ability to handle large volumes of emails isn't great."
"Jira Service Management should be more user-friendly."
"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."
"One thing I would suggest is that before we create an epic, we mention the required stories in its description. Then AI could directly create those stories instead of doing it manually inside the table, so that integration can occur."
"The product could improve its asset management."
 

Pricing and Cost Advice

"It's $69 per user per month. Only administrators need a license, and there is no limit to the number of endpoints."
"The product’s pricing is competitive and less complicated."
"The solution's pricing model is good. Also, they still follow the old concurrent licensing method."
"The cost has recently increased. It might be around $20 to $25 per user license."
"The price of the solution is becoming expensive and it should be reduced."
"It is one of the premium products on the market, but it is very costly, especially in the Indian market."
"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."
"I would suggest to always buy licenses through an Atlassian partner, so you can also rely on their expertise."
"Do not forget to calculate add-on costs. These cost a percentage of the JIRA purchasing costs and are based on the number of JIRA users."
"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."
report
Use our free recommendation engine to learn which IT Service Management (ITSM) solutions are best for your needs.
881,565 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
University
11%
Government
10%
Healthcare Company
8%
Comms Service Provider
7%
Financial Services Firm
9%
Computer Software Company
9%
Manufacturing 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

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: December 2025.
881,565 professionals have used our research since 2012.