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 Feb 2, 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)
15th
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
7.1
Number of Reviews
86
Ranking in other categories
Help Desk Software (2nd)
 

Mindshare comparison

As of May 2025, in the IT Service Management (ITSM) category, the mindshare of HaloITSM is 3.2%, up from 1.1% compared to the previous year. The mindshare of JIRA Service Management is 9.8%, down from 12.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
IT Service Management (ITSM)
 

Featured Reviews

Abhilash Sherkane - PeerSpot reviewer
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.
Karim Yousef - PeerSpot reviewer
Efficiently track and document projects with seamless tool integration
We are a management warehouse that provides services to different customers in different sectors. Primarily, we serve the banking sector and the military sector. We manage all the software delivery projects through tools such as JIRA Service Management or TFS Confluence is a great tool for…

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."
"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."
"The query language and the ability to create views of the data are very useful."
"Everyone knows how to use it, so there's no need to teach new members."
"I think one of the most valuable things is that it's all integrated."
"The initial setup is straightforward."
"The visibility features are great."
"The automations will really help the company by delegating work the way your company operates."
 

Cons

"The product does not have its own orchestration engine."
"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."
"Initially, as a completely new user, the interface was not very user-friendly, with many cluttered options."
"They need to work on the speed of Jira."
"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."
"There is room for improvement in the user interface and the queues."
"JIRA Service Management should make reporting easier. I would like something integrated with DevOps tools."
"Lacks an interface where the customer can report issues."
"JIRA protects the end-user, but for the configuration, more rules could be added to improve the workflow."
"I don't think the program is very scalable."
 

Pricing and Cost Advice

"The solution's pricing model is good. Also, they still follow the old concurrent licensing method."
"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."
"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."
"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."
"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."
"We have an annual license with JIRA Service Management, but it is billed monthly."
"JSM's pricing is one of the best, starting at around $10 per user, per month, with volume discounts available."
"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."
"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."
"It costs around $150 to $200 per user."
report
Use our free recommendation engine to learn which IT Service Management (ITSM) solutions are best for your needs.
849,686 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
13%
Government
8%
Healthcare Company
7%
Comms Service Provider
7%
Computer Software Company
19%
Financial Services Firm
10%
Manufacturing Company
8%
Government
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What is your experience regarding pricing and costs for HaloITSM?
The product’s pricing is competitive and less complicated. There is only one license cost, which includes all the components. There's no additional cost component for separate modules. It makes it ...
What needs improvement with HaloITSM?
The product does not have its own orchestration engine. If someone is looking for orchestration, they must look for an external tool.
 

Also Known As

NetHelpDesk
JIRA Service Desk
 

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