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

Ivanti Neurons for ITSM 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

Ivanti Neurons for ITSM
Ranking in Help Desk Software
13th
Ranking in IT Service Management (ITSM)
13th
Average Rating
8.2
Reviews Sentiment
6.6
Number of Reviews
17
Ranking in other categories
No ranking in other categories
JIRA Service Management
Ranking in Help Desk Software
2nd
Ranking in IT Service Management (ITSM)
2nd
Average Rating
8.2
Reviews Sentiment
6.8
Number of Reviews
88
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of February 2026, in the IT Service Management (ITSM) category, the mindshare of Ivanti Neurons for ITSM is 2.1%, up from 2.1% 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%
Ivanti Neurons for ITSM2.1%
Other90.6%
IT Service Management (ITSM)
 

Featured Reviews

Rajat_Srivastava - PeerSpot reviewer
Manager - Technical Support at a tech vendor with 10,001+ employees
Has helped streamline ticketing and change management while offering clear documentation support
Documentation and learning materials are available for Ivanti Neurons for ITSM, and if you check the vendor sites, you will find documents for each feature. I believe that short videos should be created and uploaded for newcomers to learn quickly since time can be limited. If a user believes in Ivanti, they should also believe in all its products including Ivanti Neurons for ITSM and Neurons because they are genuinely putting in hard work. This is reflected in the documentation, though I suggest they work on creating more videos. Other than that, you will find everything you need in the community site and documentation site. On a scale of 1-10, I rate Ivanti Neurons for ITSM an 8 out of 10.
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

"I like Cloud Neurons. Since it's a cloud version, it's much easier to enhance productivity because it collects all the information automatically."
"HEAT Service Management is good for asset and service desk management. It is the focal point for this solution."
"They allow us to automate ticketing processes and create requests more efficiently, improving our overall support operations."
"What I appreciate about Ivanti Neurons for ITSM is its comprehensive change request management system, which we utilize for server patching, workstation patching, BIOS updates, and driver updates, enabling us to have CAB meetings to discuss changes and approve them before implementation."
"Overall, the platform, in its abilities, is really powerful, especially now with AI as a part of hyper-automation."
"It is easy to set up."
"Everything in Ivanti Neurons for ITSM is excellent, and they are doing their best."
"The solution's technical support is excellent. I rate the technical support a ten out of ten."
"The stability of JIRA Service Management is good."
"The most valuable feature of the solution is its SLA, which everybody wants when it comes to a service-based offering."
"It is 100% stable."
"Jira Service Management has a workflow feature you can configure for your specific requirements. It also lets you efficiently manage service requests with team members."
"The most valuable feature of JIRA Service Management is a plugin we are using for the front end for simple user forms."
"JIRA Service Management provides comprehensive data management, different views with customizable dashboards, a detailed level of customization from items to workflows to roles and teams, and very flexible integration through the Atlassian marketplace plugins."
"Useful for tracking issues with development."
"I like the history, the dimensioning, and how I can configure a space based on my preferences or the project circumstances."
 

Cons

"They could provide product integration with popular platforms."
"The patching for non-Windows OSes such as Linux is poor."
"There is room for improvement in terms of response time. The support team takes a long time to respond."
"Support needs improvement in terms of responsiveness and timeliness."
"We'd like more integration with solutions like SolarWinds."
"Ivanti Neurons for ITSM is not a user-friendly tool when compared to ServiceNow."
"I believe that short videos should be created and uploaded for newcomers to learn quickly since time can be limited."
"I have had to open a few support tickets with the HEAT Service Management. They are very good but there are some areas that they could improve on."
"With Jira, we were unable to implement time-based automation in its ticketing system. We would like a feature where we can define tickets based on severity, then tickets are automatically escalated to the next level after a set period of time if they go unanswered."
"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."
"The reporting function of this solution, particularly the filters in the portal, could be improved."
"JIRA Service Management is costly."
"JSD has some analytics, but it's pretty much basic and simple dashboards. There's no mobile application for JSD. It really would benefit from better implementation with other vendors. We're heavily reliant on some external marketplace applications."
"Integration could be improved."
"The deployment can be a bit complex, especially for those who are not technical."
"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."
 

Pricing and Cost Advice

"If you want to add more users who can handle support there will be additional fees. What we call our extensions, we need to pay more for. They tell us that we need to acquire more licenses or something like that. I think it's very expensive, because in terms the pula, our local currency, it's about 20,000 per license for each user. It is an annual fee."
"I came to know from my team members that my company used to operate ServiceNow but shifted to Ivanti Neurons for ITSM due to its low licensing prices."
"The product is affordable for small businesses."
"The price is on the higher side. The support is included in the standard licensing fees."
"On a scale of one to five, where five is a good price and one is high, I would rate this solution as a three. It isn't cheap but it's not ridiculous."
"Actually in Iran we don't have copyright or intellectual property, so we can use JIRA for free."
"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."
"It costs around $150 to $200 per user."
"I price of JIRA Service Management is reasonable."
"The price of the solution is becoming expensive and it should be reduced."
"Right now, there are only two of us who are both agents on the help desk and developers. We might be on the free version because we're less than three agents or users. I'm looking at Zephyr tests, which have a $10 a month flat rate, so right now, it is $10 a month. There are lots of add-ons. They do a free version, a standard version, and a premium version. In the last company, we started on $50 a month. By the time I left, we were paying $4,500 a month. That was mainly because we had 100 users on Confluence. I bought an add-on for Jira software for which we had 10 users, and that was $5 per user per month. It was costing me $500 a month, whereas it should only be $50 a month. I don't know if licensing fee has changed. I'd like our whole company to use it, but the big problem is the licensing because the Confluence side is what is really useful, but if I add 30 users to Confluence and then buy an extension for Jira software, I've got to pay for 30 licenses, even though I've only got two users in Jira software. It is the one big disadvantage of cloud software. You always have to pay for the number of seats regardless of which product you are on. This will probably severely limit how many people would use it because I'm not going to start paying $10 per user per month for a Jira software add-on when there are only two people using it."
"It is one of the premium products on the market, but it is very costly, especially in the Indian market."
report
Use our free recommendation engine to learn which IT Service Management (ITSM) solutions are best for your needs.
882,594 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
11%
Manufacturing Company
11%
Financial Services Firm
10%
Educational Organization
8%
Financial Services Firm
9%
Computer Software Company
9%
Manufacturing Company
9%
Educational Organization
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business8
Midsize Enterprise3
Large Enterprise6
By reviewers
Company SizeCount
Small Business30
Midsize Enterprise24
Large Enterprise33
 

Questions from the Community

What do you like most about Ivanti Neurons for ITSM?
I like Cloud Neurons. Since it's a cloud version, it's much easier to enhance productivity because it collects all the information automatically.
What is your experience regarding pricing and costs for Ivanti Neurons for ITSM?
The price is on the higher side. The support is included in the standard licensing fees.
What needs improvement with Ivanti Neurons for ITSM?
Regarding analytics and reporting in Ivanti Neurons for ITSM, I am not currently using it because I primarily use the reporting functions from the Endpoint Management tool. I am not sure if there i...
 

Also Known As

HEAT Service Management
JIRA Service Desk, Atlassian Jira Service Management
 

Overview

 

Sample Customers

AFS Group, Auckland Airport, Baylor University, County of Maui, Dis-Chem Pharmacies, Elia, Essentia Health, Government Research Laboratory, Groupe Webhelp, HSBC Africa, Midwestern University
mgm technology partners, Telestream, Build.com, Zend Technologies, OfficeDrop, PGS Software, American Diabetes Association, NEPTUNE Canada
Find out what your peers are saying about Ivanti Neurons for ITSM vs. JIRA Service Management and other solutions. Updated: January 2026.
882,594 professionals have used our research since 2012.