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)
22nd
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 December 2025, in the IT Service Management (ITSM) category, the mindshare of HaloITSM is 2.7%, up from 2.1% compared to the previous year. The mindshare of JIRA Service Management is 8.0%, down from 11.5% 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 Management8.0%
HaloITSM2.7%
Other89.3%
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."
"Great to be able to create customized forms."
"The customization is the most valuable aspect of the solution. I can customize full workflows. It's very flexible. We can use mail if we want to open requests as well."
"The automation feature in JIRA Service Management is beneficial, and that's yet to be available in ServiceNow. ServiceNow doesn't have the flexibility to automate processes."
"It is 100% stable."
"This solution has helped us a great deal in project management tracking and forecasting."
"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."
"Everyone knows how to use it, so there's no need to teach new members."
"The product is not lacking anything that a QA will want to use."
 

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."
"Lacks an interface where the customer can report issues."
"The licensing model could be improved. There needs to be a different licensing model for large numbers of employees, as it remains one of the main barriers to using JIRA Service Management across our entire company."
"JIRA Service Management should make reporting easier. I would like something integrated with DevOps tools."
"If we can have an easier way to deploy this solution without the help of a consultant and a more reliable way of deploying procedures, it would be quite helpful."
"It is difficult to navigate if you don't have any prior knowledge."
"Generally requires the purchase of additional plugins."
"If JIRA were more of a substantial stand-alone product that covered more needs for project management, we wouldn't be using a suite of products."
"​SaaS version for large organizations (more than 2000 users) is not available."
 

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."
"I would rate the pricing a seven out of ten, where one is low price, and ten is high price. It's competitively priced."
"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."
"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."
"It costs around $150 to $200 per user."
"Buying a software solution is only a half part of the solution (or even less). You need to optimize usage of the software by hiring professionals who will help you to make the most of the software, especially in the beginning."
"The pricing is free for us because we are an associate partner for the product."
"I price of JIRA Service Management is reasonable."
report
Use our free recommendation engine to learn which IT Service Management (ITSM) solutions are best for your needs.
879,371 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Government
10%
University
9%
Healthcare Company
8%
Comms Service Provider
7%
Computer Software Company
10%
Financial Services Firm
10%
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.
879,371 professionals have used our research since 2012.