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 January 2026, in the IT Service Management (ITSM) category, the mindshare of HaloITSM is 2.5%, up from 2.3% compared to the previous year. The mindshare of JIRA Service Management is 7.6%, down from 11.1% 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.6%
HaloITSM2.5%
Other89.9%
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."
"JIRA SD also helps for much better feedback on the work being done. All colleagues can see what is happening."
"The query language and the ability to create views of the data are very useful."
"It scales well."
"The initial setup is pretty easy."
"What I really like about this solution, is how it manages the queues, the tickets and the routing."
"The most valuable feature of this solution is that it is user-friendly."
"The most valuable features are the management tools."
"The most valuable feature of the solution is its SLA, which everybody wants when it comes to a service-based offering."
 

Cons

"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."
"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."
"At times you will need add-ons or additional software, so built-in features would be helpful."
"If I need a new feature, JIRA requires me to pay for all users when only specific people use that add-on. I should not have to pay for everyone, so this is an area for improvement."
"The initial setup of JIRA Service Management can be complex for new users. There is a lot of configuration."
"Integration could be improved."
"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."
"The product does not have the capability to sort queued tickets by product. This would be useful in making workflows more efficient."
"Lacks an interface where the customer can report issues."
"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."
 

Pricing and Cost Advice

"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."
"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."
"It's not really expensive, especially when you compare to ServiceNow or other solutions, and it's not expensive to maintain."
"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."
"The price of the solution is becoming expensive and it should be reduced."
"But about the plugins, I found one plug-in — its name is Actionable Metric I think — and it is $3000. That is very expensive for users in Iran."
"I would suggest to always buy licenses through an Atlassian partner, so you can also rely on their expertise."
"It costs around $150 to $200 per user."
"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."
report
Use our free recommendation engine to learn which IT Service Management (ITSM) solutions are best for your needs.
881,346 professionals have used our research since 2012.
 

Top Industries

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

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,346 professionals have used our research since 2012.