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 most valuable feature of this solution is that it is user-friendly."
"It is worth its weight in gold in being able to link everything together and have everything in one place."
"The query language and the ability to create views of the data are very useful."
"The stability of JIRA Service Management is good."
"The initial setup is straightforward."
"Automation capabilities allow for automatic ticket creation using monitoring tools."
"The most valuable features are the flexibility of defining your own workflows and automation around the workflows, and the integration with the gate or any repository."
"The customer portal with connection with our knowledge base has been most valuable."
"We improved our service levels and have been able to maintain them for the last four and a half years."
"It is easy to use, cost effective, and ITIL based."
"So far, Micro Focus answers all our needs."
"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."
"It integrates well with multiple Management Information Bases (MIB's)."
"Incident management is the most valuable because we're using it to manage tickets for an accounting system."
"The initial setup is easy."
 

Cons

"If JIRA were more of a substantial stand-alone product that covered more needs for project management, we wouldn't be using a suite of products."
"The customizations in Jira could be improved by being simplified. They are currently very complex."
"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 product could improve its asset management."
"Probably the biggest downside is that you are locked into that model and you have to accept what you signed up for."
"The solution needs to be integrated better with Office X5."
"I rate Atlassian support two out of 10. It takes a lot of time to reach them and get ahold of someone who understands my problem enough to provide a solution. Also, I live in Israel, so my work week is Sunday through Thursday, but I can only contact them from Monday to Wednesday."
"We have a lot of add-ons, however, instead of the add-ons, for example, cloning could be better."
"Life cycle management is a drama."
"Same, it wasn't always stable. Actually, I wouldn't call it stable now either."
"Customization can be difficult at times because scripting is often required."
"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."
"I think one area which is the most painful from my point of view is if you need to integrate a lot of the tools, and being able to make that a lot more seamless."
"The greatest issue for us is to understand the roadmap."
"Service Manager is at the end of its life. The architecture, performance, and look are all way behind."
"There could be some slight fixes to managing the catalog, because you can customise the items so much you can't really change the items in dropdown lists easily."
 

Pricing and Cost Advice

"It depends on the number of users but it starts at $20 per month per user. I would rate them a three out of five for pricing."
"I would suggest to always buy licenses through an Atlassian partner, so you can also rely on their expertise."
"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."
"The cost has recently increased. It might be around $20 to $25 per user license."
"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."
"It costs around $150 to $200 per user."
"JIRA Service Management's pricing is pretty decent compared to competitors. I rate the pricing an eight to nine on a scale of one to ten."
"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."
"The license is not cheap."
"Micro Focus Service Manager is a little cheaper than other options. You have to pay a monthly subscription fee."
"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."
report
Use our free recommendation engine to learn which IT Service Management (ITSM) solutions are best for your needs.
893,915 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
14%
Manufacturing Company
9%
Educational Organization
6%
Computer Software Company
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,915 professionals have used our research since 2012.