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 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

JIRA Service Management
Average Rating
8.2
Reviews Sentiment
7.1
Number of Reviews
86
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

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…
MEKKAB Raouf - PeerSpot reviewer
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

"Using JIRA simplifies tracking issues and updates."
"Simplicity is a key aspect. It is not hard to use."
"The product is not lacking anything that a QA will want to use."
"The flow of the reports is good."
"Some of the most valuable features are simplicity, ease of configuration, and ease of customization."
"Using JIRA simplifies tracking issues and updates."
"Automation capabilities allow for automatic ticket creation using monitoring tools."
"It helps with time management and team management of the new tasks."
"The solution is simple to set up."
"Micro Focus Service Manager is fine. It's a good solution for small accounts with minimal reporting. Micro Focus is a good option because you don't have to worry about the budget."
"The initial setup is easy."
"It can adapt to any process in the organization."
"It helps to register things, to see the changing parts, and to correlate incidents."
"It gives us better understanding and control of service management."
"The workflow engine that standardizes and globalizes the process steps. It drives people through the process by standardization and automation."
"It's easy to scale."
 

Cons

"We have tried exporting some of the test cases into Jira from Excel. The interface for that isn't very user-friendly."
"An AI feature that enables automation and alerts for users can be an improvement."
"Jira Service Management could improve by offering more control similar to Monday.com, such as easier automations, file addition, and sharing with different people."
"It would be beneficial if we could turn comments into subtasks or other JIRA tickets directly."
"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."
"The deployment can be a bit complex, especially for those who are not technical."
"JIRA Service Management should make reporting easier. I would like something integrated with DevOps tools."
"I would like to see the user interface changed, it is not very user-friendly, and it transitions workflows."
"I don't see anything lacking."
"Micro Focus Service Manager is not very great. It would be better if it had more features. When it comes to features, BMC tops the chart. When it comes to usage, people use BMC more."
"The solution does not interface well with other products and is difficult to implement."
"It needs good integration with the configuration database, that's lacking at the moment, It's not that good."
"The interface could be better."
"Customization can be difficult at times because scripting is often required."
"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."
"Service Manager is at the end of its life. The architecture, performance, and look are all way behind."
 

Pricing and Cost Advice

"The pricing is free for us because we are an associate partner for the product."
"We may upgrade the license that we have. The license that we currently have is good for 500 agents, and it's not full yet."
"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 costs around $150 to $200 per user."
"It is a cheaply priced product."
"The price for JIRA Service Management is reasonable and cheaper than other ITSM solutions, but the licensing model is different, so you cannot compare it with other solutions. Overall, the pricing for the solution is acceptable."
"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."
"The pricing is very competitive and I think that it is okay."
"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."
"HP Service Manager has moderate pricing."
"I pay for Service Manager on a yearly basis, and the price is reasonable - I would rate it five out of ten."
"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.
838,713 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
19%
Financial Services Firm
10%
Manufacturing Company
8%
Government
7%
Computer Software Company
24%
Financial Services Firm
17%
Manufacturing Company
15%
Government
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

 

Also Known As

JIRA Service Desk
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: February 2025.
838,713 professionals have used our research since 2012.