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

Ivanti Service Desk [EOL] vs JIRA Service Management comparison

 

Comparison Buyer's Guide

Executive Summary

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 Service Desk [EOL]
Average Rating
7.6
Reviews Sentiment
6.0
Number of Reviews
8
Ranking in other categories
No ranking in other categories
JIRA Service Management
Average Rating
8.2
Reviews Sentiment
7.1
Number of Reviews
85
Ranking in other categories
Help Desk Software (2nd), IT Service Management (ITSM) (2nd)
 

Featured Reviews

Sayed Munir - PeerSpot reviewer
Beneficial connectors, useful service requests, and setup straightforward
I previously used ManageEngine. I switched because the Ivanti Service Desk has a lot of integrations and connectors which are beneficial. There are a lot of minute details where Ivanti Service Desk has an advantage over ManageEngine. For example, in ManageEngine ITSM we cannot integrate it with Oracle ERP. However, in Ivanti Service Desk we can integrate it with ERP solutions to fit in the user details, and other required objects we want. That's one of the biggest differentiators. Additionally, Ivanti Service Desk gives a lot of customization while in ManageEngine a lot of elements are hardcoded. We cannot customize it up to the minute level.
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

"Incident management and service request management features are the most valuable."
"The initial setup was quite simple; installing just took a few minutes."
"Incident management is a valuable feature."
"The tool supports a lot of standard reporting KPIs."
"The most valuable features of the Ivanti Service Desk are service requests and incident management."
"Ivanti offers us the flexibility to transform it from purely an internal IT tool to something we can use across multiple departments. There's now a queue of departments waiting to onboard and get their processes built. The flexibility within the workflow is excellent."
"The best feature is that SLAs are automatically tracked, so when we breach something, we can set up email escalations as well."
"It is highly configurable with PinkVERIFY status."
"The most valuable features are the management tools."
"We use JIRA Service Management for tracking purposes, planning, and execution."
"The most valuable features of this solution are Incident and Request Management."
"JIRA Service Management is a very user-friendly solution."
"Jira lets us customize the workflow to meet our requirements. The email and alert features are also handy."
"The product is not lacking anything that a QA will want to use."
"In Jira Service Management, the most beneficial features are process improvement, workflows, and escalations."
"Transparency of the system helps both internal and external persons involved."
 

Cons

"When we need to implement changes, it usually takes two to three days to happen, making it a very time-consuming process."
"Ivanti Service Desk could improve the GUI because it is not as good as other solutions, such as BMC or ServiceNow. If Ivanti Service Desk works on the GUI and makes it more user-friendly, and its content more attractive it might help the solution in the long run."
"You have limited ability to customize how Ivanti renders. It's a fairly strict design that doesn't offer you much freedom to alter the rigid, two-column layout on the screen. You can choose between one column or two, but that's about it. The presentation is probably the biggest weakness."
"The mobile service is minimal and doesn't provide sufficient capabilities."
"The administrative side of it could be a little more intuitive. This is the side that you use to do customizations. It is very customizable, but it could be a bit more intuitive and user-friendly. Their support can also be better in terms of response time. Currently, their response time is a little slow."
"The interface can be improved. It can be made more interactive for self-service users."
"The documentation for migration which includes migration from one version to another or cloud to on-premises is not available in detail. There is no proper planning on metadata updates. I am not able to do the data movement with the package push."
"You must be very technical to configure it."
"It is difficult to navigate if you don't have any prior knowledge."
"Jira Service Management could improve by offering more control similar to Monday.com, such as easier automations, file addition, and sharing with different people."
"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."
"The interface could be made easier to use."
"Every time there's a problem with JIRA Service Management, you have to have a look at how to solve it, and there's always a feature request or the feature request on the solution is too large and the development cycles are too slow."
"The solution needs to be integrated better with Office X5."
"JIRA Service Management could improve the forms. When you complete the form for the ticket, for example, to have more information given to the team. If they needed this information, you can give it to them. They need to add additional information for a better understanding of the whole picture of the issue or problem."
"Currently lacks an asset management module that can affect deployment."
 

Pricing and Cost Advice

Information not available
"The pricing is very competitive and I think that it is okay."
"It costs around $150 to $200 per user."
"The pricing is free for us because we are an associate partner for the product."
"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."
"Costs are about $50 per user per year. JIRA is sold in user tiers of 25, 50, 100, 250, 500, 2000, 10,000, and unlimited users. It is bad when you have 51 users then the price is based on that 100 user tier. Users at 100 will be the most cost effective."
"We have paid $20,000 recently for a one-year license for our on-prem server."
"JSM's pricing is one of the best, starting at around $10 per user, per month, with volume discounts available."
"I would rate the pricing a seven out of ten, where one is low price, and ten is high price. It's competitively priced."
report
Use our free recommendation engine to learn which IT Service Management (ITSM) solutions are best for your needs.
832,138 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Government
19%
Healthcare Company
11%
Computer Software Company
10%
Manufacturing Company
9%
Computer Software Company
19%
Financial Services Firm
9%
Manufacturing Company
8%
Government
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about Ivanti Service Desk ?
The tool supports a lot of standard reporting KPIs.
What needs improvement with Ivanti Service Desk ?
The documentation for migration which includes migration from one version to another or cloud to on-premises is not available in detail. There is no proper planning on metadata updates. I am not ab...
What is your primary use case for Ivanti Service Desk ?
Basically, we use it for service management from the financial side of things.
What do you like most about JIRA Service Management?
JIRA Service Management is a very user-friendly solution.
What is your experience regarding pricing and costs for JIRA Service Management?
While JIRA Service Management saves time, direct cost savings are challenging due to licensing fees. Currently, it costs around $150 to $200 per user, a significant expense, especially given the la...
 

Also Known As

No data available
JIRA Service Desk
 

Overview

 

Sample Customers

MBDA, Coates Hire, Perth & Kinross Council, Oil States International Inc., London Borough of Lambeth, Avon IM&T Consortium, Diagonal Consulting
mgm technology partners, Telestream, Build.com, Zend Technologies, OfficeDrop, PGS Software, American Diabetes Association, NEPTUNE Canada
Find out what your peers are saying about ServiceNow, Atlassian, ManageEngine and others in IT Service Management (ITSM). Updated: January 2025.
832,138 professionals have used our research since 2012.