No more typing reviews! Try our Samantha, our new voice AI agent.

JIRA Service Management vs OpenText Service Manager [EOL] comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Apr 5, 2026

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

JIRA Service Management
Average Rating
8.2
Reviews Sentiment
6.8
Number of Reviews
90
Ranking in other categories
Help Desk Software (2nd), IT Service Management (ITSM) (2nd)
OpenText Service Manager [EOL]
Average Rating
7.2
Reviews Sentiment
7.0
Number of Reviews
48
Ranking in other categories
No ranking in other categories
 

Featured Reviews

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.
DL
Senior Consultant Project Management & Transition at a tech services company with 501-1,000 employees
It does what it should, but it's quite outdated.
I rate Micro Focus Service Manager four out of 10. I wouldn't recommend it. I would suggest ServiceNow. There may be solutions better suited for smaller companies. There are always alternatives because the architecture isn't terribly complex. The architecture is the same across solutions, and everything is linked. There are no modules to be bought from some other company in the past and integrated. ServiceNow also its disadvantages, but if you compare it to Service Manager, I can safely say ServiceNow is the future and Service Manager is the past.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The initial setup is easy and straightforward."
"This is the most complete and versatile enterprise task management product and issue tracker."
"JIRA is an excellent tool that can cater to multiple needs and purposes, and the fact that we can use it for multiple tasks alone makes it scalable and very good at what it does."
"It's a good experience."
"This solution has helped us a great deal in project management tracking and forecasting."
"With Jira Service Desk, the simplicity of setting up a quick form and getting the service desk running quickly is very helpful."
"Our service desk is completely automated using Jira for everyone in the organization."
"JIRA can really scale perfectly for our needs."
"The application's performance reached a completely different level; so it's quite fast."
"We can have all our requests and incidents registered in one system."
"It helps to register things, to see the changing parts, and to correlate incidents."
"While the tool works, what makes it work better is I can make it do whatever they need; it's a completely customizable solution to fit with the specific needs of our organization and it does it really easily and really dependably."
"It gives us better understanding and control of service management."
"One of the big benefits that’s come out of this is a centralized view of all IT operations that really enable us to shift resources (people and money) in a real-time way to accomplish whatever we need."
"Incident management is the most valuable because we're using it to manage tickets for an accounting system. With the reports that are available, it allows us to track and identify trends at the type and item level. It also helps us in managing the workload better than what we had in Remedy, which is what we were using before 2013."
"It has an intuitive front end which allows us to roll out good customer end user experiences."
 

Cons

"JSM's ability to handle large volumes of emails isn't great."
"Integration could be improved."
"Include a split configuration in a layer part to allow cloud services to have almost full admin rights in SaaS."
"An improvement they could add is a better management dashboard."
"During the updates, when another version gets released, whatever I am tracking at that time gets lost and I have to type it all over again."
"We have tried exporting some of the test cases into Jira from Excel. The interface for that isn't very user-friendly."
"There should be some AI integrations now as AI is in the picture."
"Jira has different modules that can develop workflow for demand management and project management, but the solution is no out of the box and would require lots of customization."
"Stability was a major issue in older versions of the product."
"We aren't able to take emails that come in and turn them into tickets, especially when it comes to attachments. When an email has an attachment, like a screenshot, it is a very cumbersome process, and it does not work very well. I shouldn't have been paying technicians to cut and paste attachments from an email into the ticketing system. It should do that automatically. Other solutions are able to do that. This is something that needs to be improved. Test manager and knowledge management areas are probably amongst the worst parts of this solution. We try to use this solution for knowledge management, but it is not user-friendly. Therefore, it has limited ROI as you need to spend time to try and fully capitalize on the knowledge management system."
"It needs good integration with the configuration database, that's lacking at the moment, it's not that good."
"On the downside, it cannot really operate in the cloud; but other than that, everything is good."
"The end-user experience is very key for me. At the moment, that's an area that the product's perhaps a bit weak."
"I don't see anything lacking."
"We still find ourselves wrapping customizations around it more than we would like, and we still find the upgrade path more costly and time consuming than we would hope."
"The greatest issue for us is to understand the roadmap. We want to know whether we should upgrade now or should we wait three months."
 

Pricing and Cost Advice

"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."
"JIRA Service Desk has different pricing as it is based on agents. On average, the price is about $300 per agent."
"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."
"Jira Service Management has affordable license fees. It's $12 a month per person."
"We have an annual license with JIRA Service Management, but it is billed monthly."
"The pricing is very competitive and I think that it is okay."
"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."
"It is a cheaply priced product."
"I would say that identify your requirements and pay for the support to implement and test those requirements, and then hope that you did a good job because the cost of their service is fairly expensive."
"I pay for Service Manager on a yearly basis, and the price is reasonable - I would rate it five out of ten."
"HP Service Manager has moderate pricing."
"Micro Focus Service Manager is a little cheaper than other options. You have to pay a monthly subscription fee."
"The license is not cheap."
report
Use our free recommendation engine to learn which IT Service Management (ITSM) solutions are best for your needs.
893,311 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
14%
Manufacturing Company
9%
Computer Software Company
6%
Educational Organization
6%
Financial Services Firm
18%
Construction Company
10%
Marketing Services Firm
9%
Performing Arts
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business30
Midsize Enterprise25
Large Enterprise34
By reviewers
Company SizeCount
Small Business10
Midsize Enterprise4
Large Enterprise38
 

Questions from the Community

What is your experience regarding pricing and costs for JIRA Service Management?
While licensing is costly, setting up JIRA Service Management is overall good because the vendor helped me, and I also received support from JIRA support, making it a positive experience.
What needs improvement with JIRA Service Management?
I feel JIRA Service Management could be better if the APIs from the sponsoring team provided more support and flexibility in API endpoints. Regarding JIRA Service Management's API and support, the ...
Ask a question
Earn 20 points
 

Also Known As

JIRA Service Desk, Atlassian Jira Service Management
Micro Focus Service Manager, HPE ITSM, HPE Service Manager
 

Overview

 

Sample Customers

mgm technology partners, Telestream, Build.com, Zend Technologies, OfficeDrop, PGS Software, American Diabetes Association, NEPTUNE Canada
resultspositive, Globicon
Find out what your peers are saying about ServiceNow, Atlassian, ManageEngine and others in IT Service Management (ITSM). Updated: April 2026.
893,311 professionals have used our research since 2012.