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

JIRA Service Management vs OpenText Service Management Automation X (SMAX) comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Nov 3, 2024

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
Ranking in IT Service Management (ITSM)
2nd
Average Rating
8.2
Reviews Sentiment
7.1
Number of Reviews
83
Ranking in other categories
Help Desk Software (2nd)
OpenText Service Management...
Ranking in IT Service Management (ITSM)
16th
Average Rating
7.6
Reviews Sentiment
7.1
Number of Reviews
6
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of January 2025, in the IT Service Management (ITSM) category, the mindshare of JIRA Service Management is 11.5%, down from 12.0% compared to the previous year. The mindshare of OpenText Service Management Automation X (SMAX) is 2.2%, up from 0.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
IT Service Management (ITSM)
 

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…
Mourad Ali - PeerSpot reviewer
Offers topic analytics for incident and problem management
The only challenge with Azure customers is when they have a specific requirement that is not available out of the box and is inflexible to adjust. Sometimes, customers have tough requirements that are not flexible enough to be adjusted, even if SMAX can provide a better alternative. They need this specific feature. This challenge is common with SMAX, BMC, ServiceNow, IBM, or other similar tools. When working with enterprise tools that are not developed in-house, I don't have access to the source code and am limited to the features and capabilities provided by the leading vendors. So, this challenge is common across SMAX, BMC, and ServiceNow. The solution could have more customization flexibility.

Quotes from Members

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

Pros

"JSM's best feature is the integration with other Jira products."
"The customization is the most valuable aspect of the solution. I can customize full workflows. It's very flexible. We can use mail if we want to open requests as well."
"What I really like about this solution, is how it manages the queues, the tickets and the routing."
"We use JIRA Service Management for tracking purposes, planning, and execution."
"The most valuable feature of JIRA Service Management is a plugin we are using for the front end for simple user forms."
"The initial setup is easy and straightforward."
"It's easy to set up the solution."
"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."
"The most valuable features of Micro Focus Service Management Automation X (SMAX) are that it is user-friendly, easy to configure, and adaptable."
"It offers a range of tools for sales and configuration. It's like a business process improvement platform, suitable for various lines of business operations."
"The tool is very easy to use."
"OpenText Service Management Automation X provides valuable features such as topic analytics for incident and problem management. It also includes natural language processing for analyzing technical descriptions. Additionally, it features a virtual chatbot capable of processing natural language to interact effectively with end users. This service enhances customer support and is not subject to the limitations often found in offerings from other vendors."
"This is a cordless application that can be used throughout any organization."
"The product provides an interface for the end users to make requests."
 

Cons

"JIRA Service Management should make reporting easier. I would like something integrated with DevOps tools."
"JSM's ability to handle large volumes of emails isn't great."
"The initial setup is very complex."
"There should be better connections with access management. They should improve the connectivity."
"Generally requires the purchase of additional plugins."
"Its UI is a bit overwhelming for new users. That has been the problem with Jira for a long time. If they could put some fields that we could use to simplify the UI, it would be good."
"It has change management and incident management, but CMDB is not there. It's also not as user-friendly as ServiceNow."
"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 solution lacks sufficient documentation."
"The tool has negatively impacted our productivity."
"The contract management feature can be improved."
"The initial setup of Micro Focus Service Management Automation X (SMAX) is complicated, but once it is set up the configuration is straightforward to adapt to the users' or customers' needs."
"The product's connectivity with third-party products is an area of concern where improvements are required."
 

Pricing and Cost Advice

"Licensing can become quite expensive."
"The pricing is free for us because we are an associate partner for the product."
"It is one of the premium products on the market, but it is very costly, especially in the Indian market."
"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."
"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'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 rate the pricing a seven out of ten, where one is low price, and ten is high price. It's competitively priced."
"This is pricey solution. Should we move to using all cloud solutions in our business, we may move to different tools that have multiple functionality versus having a solution for each area. This would be too pricey and we would need to replace Jira with a different solution that also offers other features."
"The cost of the license for SMAX varies depending on the configuration, including the number of seats for users and the customer's specific requirements. It's not a fixed cost and can vary."
"The solution is somewhat cheaper than the competitors."
report
Use our free recommendation engine to learn which IT Service Management (ITSM) solutions are best for your needs.
831,265 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
19%
Financial Services Firm
9%
Manufacturing Company
8%
Government
7%
Computer Software Company
21%
Financial Services Firm
11%
Government
8%
Manufacturing Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What do you like most about JIRA Service Management?
JIRA Service Management is a very user-friendly solution.
What is your experience regarding pricing and costs for JIRA Service Management?
While JIRA Service Management saves time, direct cost savings are challenging due to licensing fees. Currently, it costs around $150 to $200 per user, a significant expense, especially given the la...
What is your primary use case for Micro Focus Service Management Automation X (SMAX)?
The solution is used for the end-user portal. It is used for incident management, requests, and other informational purposes.
What advice do you have for others considering Micro Focus Service Management Automation X (SMAX)?
The tool is appropriate if we don't have a complicated use case. It is the right tool for simple use cases. It's a lot cheaper than ServiceNow. It is an appropriate tool for a smaller business or m...
 

Also Known As

JIRA Service Desk
OpenText Service Manager, Micro Focus Service Management Automation X (SMAX)
 

Interactive Demo

Demo not available
 

Overview

 

Sample Customers

mgm technology partners, Telestream, Build.com, Zend Technologies, OfficeDrop, PGS Software, American Diabetes Association, NEPTUNE Canada
Zurich Airport, Envirosuite, Norsk Helsenett, Achmea, University of Milan, World Vision, Petroleum Development Oman, Court of Justice of the Federal District and Territories (TJDFT).
Find out what your peers are saying about JIRA Service Management vs. OpenText Service Management Automation X (SMAX) and other solutions. Updated: January 2025.
831,265 professionals have used our research since 2012.