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.0
Number of Reviews
87
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

"Transparency of the system helps both internal and external persons involved."
"Using JIRA simplifies tracking issues and updates."
"The simplicity is good for our clients. The price is good."
"It scales well."
"Jira gets the basics right in terms of the product backlog and a scrum board teams can use to manage sprint backlogs."
"Its integration is most valuable. It is pretty open for integration."
"We have found the issue type feature particularly valuable, as it provides an out-of-the-box solution that aligns with our needs."
"JIRA SD also helps for much better feedback on the work being done. All colleagues can see what is happening."
"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."
"The design has been revamped in terms of GUI. The current interface is quite easy to read."
"It can adapt to any process in the organization."
"It gives us better understanding and control of service management."
"Technical support is pretty good."
"Service Manager gives us a single system where everything is centralized in one base."
"Service Manager's best features are flexibility and customizability."
"The solution is simple to set up."
 

Cons

"When you raise a ticket with Jira, there's no ability to see your other JIRA tickets."
"The licensing model could be improved."
"An improvement they could add is a better management dashboard. We only use the dashboard for the administration mode. We have a dashboard that reports the state of bugs or requirements. However, customers can only view requests that they made. We are not able to share a dashboard with our manager level customers to show them all of the requests in a quick dashboard."
"It should be easier to log in."
"At times you will need add-ons or additional software, so built-in features would be helpful."
"From the customer side, it's not friendly used compared to other competitors, like ServiceNow or BMC. It's also not fully ITSM management if you compare it with ServiceNow or BMC. They have a full model of ITSM. In BMC they have TrueSight, they have Discovery, which helps IT to discover IT equipment with a serial number, with the specs, capacity of the server."
"Jira Service Management should be more user-friendly."
"Integration possibilities with other products that are not Atlassian would be helpful. Support should also provide separate installation guides for each product even though they are easy to install."
"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, still, has a bit of more of improvement possibilities in the codeless part. But, I can see that they are working on it, so that's quite good as well."
"The interface could be better."
"Their end-user interface and technical support features could be improved."
"I think the best recommendation to Micro Focus would be to increase awareness and the marketing for this product."
"Service Manager is at the end of its life. The architecture, performance, and look are all way behind."
"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."
"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

"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."
"The price of the solution is becoming expensive and it should be reduced."
"The pricing is free for us because we are an associate partner for the 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."
"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."
"Jira Service Management has affordable license fees. It's $12 a month per person."
"I price of JIRA Service Management is reasonable."
"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."
"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."
"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."
"HP Service Manager has moderate pricing."
"The license is not cheap."
report
Use our free recommendation engine to learn which IT Service Management (ITSM) solutions are best for your needs.
867,445 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
17%
Financial Services Firm
9%
Manufacturing Company
8%
Educational Organization
6%
Computer Software Company
24%
Manufacturing Company
10%
Performing Arts
9%
Educational Organization
6%
 

Company Size

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

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, BMC and others in IT Service Management (ITSM). Updated: September 2025.
867,445 professionals have used our research since 2012.