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 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)
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
88
Ranking in other categories
Help Desk Software (2nd)
 

Mindshare comparison

As of April 2026, in the IT Service Management (ITSM) category, the mindshare of HaloITSM is 2.2%, down from 2.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%
HaloITSM2.2%
Other90.5%
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 query language and the ability to create views of the data are very useful."
"It's easy to use and the fastest way to handle a ticketing system."
"Some of the most valuable features are simplicity, ease of configuration, and ease of customization."
"I'm mainly working in the ITSM module of JIRA Service Management, and the integration between the system incident and how you can link all the records to the change makes it quite powerful."
"The automations will really help the company by delegating work the way your company operates."
"JIRA Service Management is much better than the normal JIRA software that we had, as it is much more controlled and allows for different kinds of customization that we can plan and implement based on the project requirements."
"The solution is scalable; we have currently deployed it to about 35 agents and it will be deployed to around 1200 customers, all of them dealing with creating and resolving tickets."
"With Jira Service Desk, the simplicity of setting up a quick form and getting the service desk running quickly is very helpful."
 

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."
"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."
"Jira Service Management should be more user-friendly."
"It would be better if it had capabilities to connect to mobile applications (e.g., Whatsapp)"
"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 performance in cloud service management could be improved. For example, sometimes queries get stuck, and when you search for a specific thing, it freezes until you refresh the page."
"The product could improve its asset management."
"A lot of users have said that they want a feature that was on the on-prem version of Jira and the vendor can't deliver. They're either unwilling or unable to give feature parity."
"As a consultant, I have used the support. Some of the support I have received has been good and other times it could improve."
 

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."
"It costs around $150 to $200 per user."
"On a scale of one to five, with one being really high and five being good, I would rate the price of this solution as a four."
"The cost has recently increased. It might be around $20 to $25 per user license."
"Licensing can become quite expensive."
"We have an annual license with JIRA Service Management, but it is billed monthly."
"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."
"JIRA Service Desk has different pricing as it is based on agents. On average, the price is about $300 per agent."
"The price for JIRA Service Management is reasonable and cheaper than other ITSM solutions, but the licensing model is different, so you cannot compare it with other solutions. Overall, the pricing for the solution is acceptable."
report
Use our free recommendation engine to learn which IT Service Management (ITSM) solutions are best for your needs.
885,728 professionals have used our research since 2012.
 

Top Industries

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

Questions from the Community

Ask a question
Earn 20 points
What needs improvement with JIRA Service Management?
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, t...
 

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: March 2026.
885,728 professionals have used our research since 2012.