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

JIRA Service Management vs OpenText Service Manager [EOL] 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

JIRA Service Management
Average Rating
8.2
Reviews Sentiment
6.8
Number of Reviews
88
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.
MEKKAB Raouf - PeerSpot reviewer
Information Technology Service Manager & Technology Integration DevOps at Djezzy
Excellent pricing with great change management and service management capabilities
We started with version 9.3, and now we're on 9.6 with the full solution, including the CMS. They have lots of options. They propose a full solution for technology and IT service management. We are a telecom company. We are a leader in the market, and therefore, we need to have all details about our own environment and assets. So far, Micro Focus answers all our needs. I'd advise new users to go directly to the SMAX solution, the last, last version of Service Manager. If they are a technical company or information technology company with engineers and developers, they can use it on-premise. If they don't have such competence in the company, they can ask for the solution on the cloud. It is easily available on Microsoft, Amazon, or Google clouds. I'd rate the product nine out of ten.

Quotes from Members

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

Pros

"We use JIRA Service Management for tracking purposes, planning, and execution."
"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."
"Two features I like about Jira are its ticketing system and its compatibility with Confluence. Also, the Knowledge Base is one of the more valuable features that would really benefit us."
"This is the most complete and versatile enterprise task management product and issue tracker."
"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 simplicity is good for our clients."
"The product is not lacking anything that a QA will want to use."
"Easily integrates with other tools."
"It has features such as integration with Skype for Business, smart analytics, and smart ticketing."
"We improved our service levels and have been able to maintain them for the last four and a half years."
"Service Manager's best features are flexibility and customizability."
"A valuable feature for us is that we have an ordered way to handle all the cases that we can handle with the infrastructure."
"The solution is simple to set up."
"HP products generally have always been stable, and this is no different."
"Technical support is pretty good."
"It helps to register things, to see the changing parts, and to correlate incidents."
 

Cons

"The product could improve its asset management."
"Initially, as a completely new user, the interface was not very user-friendly, with many cluttered options."
"I think the performance can be better."
"There should be better connections with access management. They should improve the connectivity."
"The queries are weak and lack advanced functionality. You can do rudimentary queries, but you can't aggregate. You can't filter for a lot of things that would be useful, so you need to use plugins to write writing advanced queries. I run into problems when working with different organizations because they always have restrictions on what kind of plugins they allow."
"I think there are other IT ticketing tools that are better in terms of routing or workflows than Jira Service Desk."
"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."
"In general, JIRA has no relation to customers or financials. Therefore, marketplace add-ons are needed to make it work for customer-facing systems."
"The user interface is very clunky."
"It's not so easy to move to the next version. It's not quick to upgrade."
"Pure cloud-based native functionality is lacking."
"It needs to be easier to use for the end users because one problem we had was that we are handling different kinds of cases."
"It's not user friendly (too complex), and it gives limited guidance documentation of how to filter all the logs detected."
"On the downside, it cannot really operate in the cloud; but other than that, everything is good."
"It, still, has a bit of more of improvement possibilities in the codeless part."
"The stability could be better."
 

Pricing and Cost Advice

"But about the plugins, I found one plug-in — its name is Actionable Metric I think — and it is $3000. That is very expensive for users in Iran."
"The price of JIRA Service Management could be reduced."
"Do not forget to calculate add-on costs. These cost a percentage of the JIRA purchasing costs and are based on the number of JIRA users."
"I rate Service Management four out of 10 for affordability. The price could be better, especially for companies using more than one Atlassian product. It's suitable for SMBs that can afford it. I don't think there's another tool that's both better and cheaper. All help desk tools are relatively expensive."
"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."
"Jira Service Management has affordable license fees. It's $12 a month per person."
"The pricing is free for us because we are an associate partner for the product."
"I would suggest to always buy licenses through an Atlassian partner, so you can also rely on their expertise."
"HP Service Manager has moderate pricing."
"The license is not cheap."
"I pay for Service Manager on a yearly basis, and the price is reasonable - I would rate it five out of 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."
"Micro Focus Service Manager is a little cheaper than other options. You have to pay a monthly subscription fee."
report
Use our free recommendation engine to learn which IT Service Management (ITSM) solutions are best for your needs.
884,933 professionals have used our research since 2012.
 

Top Industries

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

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business30
Midsize Enterprise24
Large Enterprise33
By reviewers
Company SizeCount
Small Business10
Midsize Enterprise4
Large Enterprise38
 

Questions from the Community

What needs improvement with JIRA Service Management?
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, t...
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: March 2026.
884,933 professionals have used our research since 2012.