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

"One of the best things about JIRA is that it searches for answers while questions are being typed so some tickets do not need to be submitted."
"Service Management is great if you're an Atlassian shop already using JIRA for the development team and you want another tool for help desk ticketing. When it's all under the same umbrella, I can easily take a ticket from the help desk and move it to the development team. You can't beat that integration between two products."
"What I really like about this solution, is how it manages the queues, the tickets and the routing."
"The initial setup is straightforward."
"JIRA SD also helps for much better feedback on the work being done. All colleagues can see what is happening."
"With Jira Service Desk, the simplicity of setting up a quick form and getting the service desk running quickly is very helpful."
"I think one of the most valuable things is that it's all integrated."
"The most valuable features of this solution are Incident and Request Management."
"Service Manager's best features are flexibility and customizability."
"We can have all our requests and incidents registered in one system."
"The design has been revamped in terms of GUI. The current interface is quite easy to read."
"Technical support is pretty good."
"It gives us better understanding and control of service management."
"Its flexibility and ease of customization are its most valuable features."
"Service Manager does what it should, but it's quite outdated."
"It can adapt to any process in the organization."
 

Cons

"It would be useful to be ale to link tickets across different gantt charts in Jira and Confluence."
"Initially, as a completely new user, the interface was not very user-friendly, with many cluttered options."
"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."
"If I need a new feature, JIRA requires me to pay for all users when only specific people use that add-on. I should not have to pay for everyone, so this is an area for improvement."
"Usability needs improvement. To configure it, you need to be well versed in Jira administration. It's not very intuitive."
"The main issue with this solution is there's no limited subscription available for plugins we only use for a few people. If we only have a team of twenty using a plugin, we still have to purchase a subscription for the whole 200 users."
"I don't think the program is very scalable."
"​SaaS version for large organizations (more than 2000 users) is not available."
"I think the best recommendation to Micro Focus would be to increase awareness and the marketing for this product."
"Pure cloud-based native functionality is lacking."
"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."
"Service Manager is at the end of its life. The architecture, performance, and look are all way behind."
"The user interface is very clunky. It's only now beginning to be a web-based interface, but for now it's still very clunky."
"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."
"There's a lot of manual work, which is error prone and time consuming, in how the code gets transported from one system to the other."
"The interface could be better."
 

Pricing and Cost Advice

"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 license we use is on a yearly basis. As a Solution Partner, we were using the free one and were using the free plugins. We were also giving our own plugins to the Atlassian Solution Partners for free. We don't pay anything to Atlassian."
"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."
"The cost has recently increased. It might be around $20 to $25 per user license."
"We have an annual license with JIRA Service Management, but it is billed monthly."
"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."
"We need a license because we have a higher number than the free part."
"On a scale of one to five, with one being really high and five being good, I would rate the price of this solution as a four."
"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."
"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."
report
Use our free recommendation engine to learn which IT Service Management (ITSM) solutions are best for your needs.
847,772 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
19%
Financial Services Firm
10%
Manufacturing Company
8%
Retailer
7%
Computer Software Company
25%
Manufacturing Company
16%
Financial Services Firm
15%
Government
10%
 

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: March 2025.
847,772 professionals have used our research since 2012.