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

BMC Helix Enterprise Service Management vs JIRA Service Management comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jun 15, 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

BMC Helix Enterprise Servic...
Ranking in IT Service Management (ITSM)
24th
Average Rating
7.0
Reviews Sentiment
4.8
Number of Reviews
1
Ranking in other categories
No ranking in other categories
JIRA Service Management
Ranking in IT Service Management (ITSM)
2nd
Average Rating
8.2
Reviews Sentiment
7.1
Number of Reviews
86
Ranking in other categories
Help Desk Software (2nd)
 

Featured Reviews

KV
Utilize comprehensive IT service modules while addressing configuration database issues
There are several areas where BMC Helix Enterprise Service Management could be improved. Currently, ServiceNow has an edge when it comes to the ease of discovering Configuration Items (CIs). In BMC Helix, there are issues with the Configuration Management ( /categories/configuration-management ) Database (CMDB ( /categories/configuration-management-databases )), such as duplicate entries and problems with reconciliation. The recently introduced dashboard tool in Helix, which replaced Smart Reporting ( /categories/reporting ), has several issues. Reporting ( /categories/reporting ) has been a consistent problem in BMC, and it would greatly benefit from enhancements.
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…

Quotes from Members

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

Pros

"The support of BMC is generally good and better compared to some competitors."
"Automation capabilities allow for automatic ticket creation using monitoring tools."
"We have found the issue type feature particularly valuable, as it provides an out-of-the-box solution that aligns with our needs."
"The links between the help desk and Jira issues and between Confluence and Jira issues are most valuable. I can write requirements in Confluence and link them to user stories in Jira and test cases. I can see my test coverage and all that kind of stuff. The integration between these three is very useful. It is pretty customizable, and it integrates well. There are a lot of add-ins and a lot of connectors to third-party products. In my last company, we used Test Royal for managing all the tests, and it integrated perfectly with that. For any issue or bug, we could see what tests have been run and the complete history of the tests."
"The stability of JIRA Service Management is good."
"The SLA, speed, the comments from agents' side, and the dashboard for agents are the most valuable features."
"It is much more controlled and allows for different kinds of customization that we can plan and implement based on the project requirements."
"JSM's best feature is the integration with other Jira products."
"It's easy to set up the solution."
 

Cons

"There are several areas where BMC Helix Enterprise Service Management could be improved. Currently, ServiceNow has an edge when it comes to the ease of discovering Configuration Items (CIs)."
"The initial setup of JIRA Service Management can be complex for new users. There is a lot of configuration."
"It has change management and incident management, but CMDB is not there. It's also not as user-friendly as ServiceNow."
"The interface could be made easier to use. While it is not the worst, there is still room for improvement."
"It would be useful to be ale to link tickets across different gantt charts in Jira and Confluence."
"Integration could be improved."
"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."
"Usability needs improvement. To configure it, you need to be well versed in Jira administration. It's not very intuitive."
"The performance in cloud service management could be improved."
 

Pricing and Cost Advice

Information not available
"We need a license because we have a higher number than the free part."
"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."
"Jira Service Management has affordable license fees. It's $12 a month per person."
"Actually in Iran we don't have copyright or intellectual property, so we can use JIRA for free."
"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."
"We have an annual license with JIRA Service Management, but it is billed monthly."
"It costs around $150 to $200 per user."
"I would rate the pricing a seven out of ten, where one is low price, and ten is high price. It's competitively priced."
report
Use our free recommendation engine to learn which IT Service Management (ITSM) solutions are best for your needs.
862,077 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Computer Software Company
18%
Financial Services Firm
10%
Manufacturing Company
9%
Government
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What is your experience regarding pricing and costs for BMC Helix Enterprise Service Management?
While I am not very sure about the pricing, I have heard that the license cost of BMC is relatively lower than its competitors.
What needs improvement with BMC Helix Enterprise Service Management?
There are several areas where BMC Helix Enterprise Service Management could be improved. Currently, ServiceNow has an edge when it comes to the ease of discovering Configuration Items (CIs). In BMC...
What is your primary use case for BMC Helix Enterprise Service Management?
I use BMC Helix Enterprise Service Management ( /products/bmc-helix-enterprise-service-management-reviews ) primarily for IT service management. It supports modules like incident management, change...
 

Also Known As

No data available
JIRA Service Desk
 

Overview

 

Sample Customers

Information Not Available
mgm technology partners, Telestream, Build.com, Zend Technologies, OfficeDrop, PGS Software, American Diabetes Association, NEPTUNE Canada
Find out what your peers are saying about ServiceNow, Atlassian, BMC and others in IT Service Management (ITSM). Updated: June 2025.
862,077 professionals have used our research since 2012.