No more typing reviews! Try our Samantha, our new voice AI agent.

JIRA Service Management vs ServiceNow vs xMatters 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:
 

Mindshare comparison

IT Service Management (ITSM) Mindshare Distribution
ProductMindshare (%)
JIRA Service Management7.3%
ServiceNow15.8%
BMC Helix ITSM5.7%
Other71.2%
IT Service Management (ITSM)
IT Service Management (ITSM) Mindshare Distribution
ProductMindshare (%)
ServiceNow15.8%
JIRA Service Management7.3%
BMC Helix ITSM5.7%
Other71.2%
IT Service Management (ITSM)
IT Alerting and Incident Management Mindshare Distribution
ProductMindshare (%)
xMatters6.0%
PagerDuty Operations Cloud13.1%
Opsgenie9.1%
Other71.8%
IT Alerting and Incident Management
 

Featured Reviews

Sohaib Ahmad - PeerSpot reviewer
Vice President Service Delivery at quixel
Comprehensive workflows and data views have supported complex teams but still need cost improvements
JIRA Service Management is costly. The pricing structure needs improvement. When I add some plugins, I have to pay the cost for every user whether they are using it or not. For smaller companies, the detailed workflow editing and the kind of details that JIRA Service Management provides would be complex. For startups and smaller companies, JIRA Service Management would be complex. The cloud offering is easier because I don't have to manage the infrastructure. There are two templates of the project: company-managed and team-managed. Team-managed is a newer feature, which is good for startup-kind companies where they don't need control over data from multiple projects displaying in one dashboard. For startups, JIRA Service Management is somewhat complex with its schemes and everything. Capacity management should be improved in terms of additional features in the next release of JIRA Service Management.
MT
Manager of Security Engineering & Architecture at a outsourcing company with 5,001-10,000 employees
Seamless data integration and advanced automation improve service delivery efficiency
I think that nothing needs to be improved with the product; you just need the user to commit and spend appropriate time to overcome that learning curve. Once that is done, the product itself is pretty wonderful. I've seen a very nicely built interface with ServiceNow, and I've also seen the ugliest version that feels outdated. ServiceNow does allow that team to exist. They should modernize their fonts and their layout, the UI friendliness. They did introduce AI, chatbots, and AI on the back end, so that's wonderful and extremely useful if you train it. If you don't train it, it's pretty useless. Assessing the impact of ServiceNow's automation on service delivery times is complicated. The engineers who operate on ServiceNow find it isn't straightforward because the data set is accessible by everybody. The problem is that understanding how to manage that data set requires an enormous amount of engineering skill set to run the product. I would not hand the key to the customer; I would highly recommend that ServiceNow take control of that. Instead of offering support for the software, they should offer administrative support for the software. They should provide professional service or some kind of support system that allows us to use their product at a faster pace. I'm sure they offer something, but it's often outrageously expensive, or they rely on another company to resell their product and offer professional service. It makes no sense in my opinion, and they should offer the team at the front to help customize the product to fit each company's needs, as every company has different demands and forms of submitting a request that need adjustment over time.
reviewer1855452 - PeerSpot reviewer
Infrastructure Analyst at a financial services firm with 10,001+ employees
Helps in ensuring that everyone gets notified when needed, and provides the flexibility to integrate it and build what we want on top of it
They recently released an incident module that allows users, or at least teams, to track major incidents and other things, and you can send out communication via that one webpage. You can engage on-call teams and communicate to stakeholders as well, but one thing that is missing there is a group chat. If there is a group chat on the same webpage that all of the support teams could use, it would be a one-stop shop that all of the major incident managers would use as their product to manage a major incident. Without that, at the moment, they are mainly referring to teams and then adding data into xMatters as and when they can. Some of the workflow development work that we do for the in-house piece can be quite complicated if you don't have experience using the tool. You have to have to go through the documentation, but I suppose that's an expectation. When users first log on and they're configuring the rotas, it does take them a bit of time to get their heads around how to configure the shifts. Some of them do need guidance. We have got a support document, and xMatters also has a support page where they can go and read through the details. Our roles and access for each user are locked down, as opposed to just letting them access the xMatters portal because it can add more confusion because the support portal explains that they can do X, Y, and Z. So, we're removing that ability, but once the users get their head around how to configure the rotas, the overall intuitiveness of the UI is pretty good. It is simple and clean, and they don't have to do that many steps. There are probably one or two group supervisors that configure the rotas, and the rest of them log on. We've already pre-populated the contact details from our directory, so usually, they'll just go and add a personal device, if they do want to get called on a personal device, or they want to set up the app, which is pretty easy using the QR codes. The product looks nice and clean. The only thing is that it takes a little bit of work to get your head around the rotas, but once you do, it's pretty darn simple.

Quotes from Members

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

Pros

"My advice to users is that JIRA Service Management is a good project management tool to handle projects respectively and efficiently."
"Its integration is most valuable. It is pretty open for integration."
"The centralized feature allows us to track test cases and integrate with automation and bug fixing."
"The simplicity is good for our clients. The price is good."
"We have an Agile environment and using Jira makes it easy to adhere to Agile best practices."
"JIRA Service Management provides comprehensive data management, different views with customizable dashboards, a detailed level of customization from items to workflows to roles and teams, and very flexible integration through the Atlassian marketplace plugins."
"It is worth its weight in gold in being able to link everything together and have everything in one place."
"Developing processes is easy and user-friendly."
"The solution has very good automation tools."
"The feature that I have found most valuable from ServiceNow is the ability to assign sub-tasks to different teams, including problem tickets and the regular and chain tasks."
"In 12 years, I've rarely seen a failure of their cloud hosting, if ever."
"ServiceNow is the best ticketing tool I have used so far."
"We can keep track of incidences. There is a bucket where we keep all our information, and it enables communication between stakeholders. It helps us collaborate with each other."
"Very good incident management, chain management and problem management features."
"Compared to HPE Service Manager, ServiceNow offers a lot more customizations and a lot more plug-ins that you can throw in there."
"It is a very promising product, they have a new release every six months, they're investing quite a lot, and you can do many creative things with the product."
"It is the sort of thing that we can't live without anymore."
"I don't think I've ever had a complaint about it; xMatters just works."
"Probably the most important one is that it persists in attempting to contact to someone until someone is engaged on the event."
"It has been easy to use and very reliable."
"xMatters provides targeted, content-rich notifications to reduce response times in our organizations."
"One of the things that really attracted me is in workflows, you can write your own custom steps in JavaScript. You are not restricted to the steps that they provide. If you can write it in JavaScript, you can pretty much do anything. It gives me flexibility in ways that other platforms don't. For example, the online dashboard system we use is not a widely used one, but they have an API. So, I'm able to write the JavaScript steps to do things like check if a system's in the maintenance window or create an instant on the dashboard or change the status of an instant. I'm not dependent on the dashboard provider or xMatters creating steps for me."
"It reduces the amount of oversight required, and consequently, the amount of time to assign and get a response on a ticket."
"It helped change behavior across the organization to improve accountability."
 

Cons

"Jira Service Management could improve by offering more control similar to Monday.com, such as easier automations, file addition, and sharing with different people."
"During the updates, when another version gets released, whatever I am tracking at that time gets lost and I have to type it all over again."
"The documentation needs improving, it's difficult to find specific procedures."
"It is difficult to navigate if you don't have any prior knowledge."
"You can use different plug-ins for JIRA Service Desk to add some functionality, but these plug-ins are very expensive."
"With Jira, we were unable to implement time-based automation in its ticketing system."
"The product is supposed to include an interface where the customer can report issues, things they cannot resolve easily. It's not there at the moment so it's more difficult to resolve issues with the OEMs."
"I feel that Atlassian isn't really interested in fixing everything because if they did, the partners that are developing the fixes and features would not have a place in the market."
"I am interested to see the firm's strategic plans for Artificial Intelligence (AI) and Machine Learning (ML), and how the particular areas it will expand on from its existing investments (that feature, for example, in its ITSM Pro and CSM Pro modules)."
"They can maybe improve the area of agile project management. They do have user storyboards and other things, but we kind of lean on Jira for that work."
"The licensing needs to be divided into tiers in order to attract lower-level users."
"ServiceNow's mobile app should be seamless and it is not right now."
"ServiceNow's mobile app should be seamless and it is not right now."
"The solution could improve by making the CMDB integrate with a CI better to allow it to be seen across multiple platforms."
"HR Service Management is one module that needs a lot of improvement because it's a pretty new module. It was introduced in the last two years. It's becoming more mature day by day, but there is a lot of scope for improvement in that module."
"ServiceNow is such a complex piece of software. It's trying to be everything."
"The reporting functionality could be improved, as it can be somewhat restrictive sometimes."
"I've asked for the ability to have tags on groups, and for dynamic lists, meaning the ability to pull data from another location and use it in xMatters dynamically."
"It has not improved our organization."
"Support may take longer than desired to resolve some issues."
"It took me awhile to get used to whatever was available in the interface. The interface from two years ago was a bit more confusing when looking at where you should go"
"In terms of intuitiveness and flexibility of xMatters when it comes to customizing on-call schedules, rotations, and escalations, for me, as an IT professional, setting it up isn't that big of a deal, but I understand that some people struggle with it because when you get wrapped up into it. You can get lost. It's not super complex, but it's complicated enough to the point where you can say that you should have done it another way. The shift part can be confusing for some people. In that respect, one of the shortcomings my team has found is when we have to add another person, such as a new hire, to xMatters, we can't add them to a group within xMatters without having to put them on a shift. If we put them in a group, they have to be on-call. We can create their account, and then they're just out there in limbo until their team says, "You have to be on this shift." One piece of feedback for xMatters is to figure out how to have manageable groups so that they're contactable from xMatters. They do not necessarily have to be on a shift right from the start or at all for that matter."
"I would like to see some more user templates. There are roles — administrator, user, etc. — but it would be nice to create a user template that restricted what people assigned that role could do."
"An additional knowledge-sharing program could be helpful and part of the demo workshops (right now, these only provide partial information)."
 

Pricing and Cost Advice

"We have an annual license with JIRA Service Management, but it is billed monthly."
"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."
"Licensing can become quite expensive."
"I price of JIRA Service Management is reasonable."
"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."
"We have paid $20,000 recently for a one-year license for our on-prem server."
"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."
"The solution is expensive."
"I am from Brazil. For Latin American markets, ServiceNow is very expensive as compared to other vendors, such as VMware."
"The licensing expenses are excessively high."
"The pricing is on the high side, but if you look at the stability and option to work, it's kind of justified."
"I know that it's not too bad because people continue to use it and they are happy to renew up their contract."
"The first impact for the customer is that it is expensive, but do not forget that it is a solution that includes infrastructure; a single cost, easy to justify."
"The product cost is higher than that of other vendors."
"Certainly, from a product-platform perspective, the price is not too bad."
"The only potential concern is professional services. They are capable, but like to bill on an hourly basis."
"You should perhaps arrange an evaluation or trial to just test it out. Get your feet wet. That is so important. If you don't try it, then you won't know."
"Then, in pricing, you are limited on your number of SMS messages that you can send a month and the licensing cost annually."
"If you are willing to pay for the licensing of it, it is able to scale out.​"
"The cost depends very much on the company's size and usage. We're a very high use case compared to many companies, so we had to consider licensing costs carefully. If we added all our users, that would be 30,000, and that's no good; we wouldn't have been able to afford it. For example, we had to put in customization to sync across on-call users. For the license per user, the price is very reasonable and comparable to ServiceNow when factoring in everything that needs to get up and running."
"​I do not think it is worth the value.​"
"It feels like good value in the sense that the service is excellent. The people above me who look at such things have renewed it a couple of times, and I think they would have thought whether it was good value, whether it was wildly overpriced, or whether there were better and cheaper alternatives. So, from that perspective, the pricing is fair and proper."
"There's a significant difference between a full license, which allows people to respond to and acknowledge receipt of messages, and a more scaled-down license, which just allows people to see the notification. So we need to evaluate what license they need when onboarding new users because the full license is significantly more expensive."
report
Use our free recommendation engine to learn which IT Service Management (ITSM) solutions are best for your needs.
885,789 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
14%
Manufacturing Company
9%
Computer Software Company
7%
Educational Organization
7%
Financial Services Firm
12%
Manufacturing Company
10%
Computer Software Company
8%
Government
8%
Performing Arts
12%
Financial Services Firm
9%
Manufacturing Company
8%
Healthcare Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business30
Midsize Enterprise24
Large Enterprise33
By reviewers
Company SizeCount
Small Business55
Midsize Enterprise35
Large Enterprise169
By reviewers
Company SizeCount
Small Business4
Midsize Enterprise2
Large Enterprise24
 

Questions from the Community

What needs improvement with JIRA Service Management?
JIRA Service Management is costly. The pricing structure needs improvement. When I add some plugins, I have to pay th...
Which solution is better for developing non-ITSM applications: OutSystems or Service Now?
The short answer is that OutSystems is far better for 2 main reasons. Firstly, with Service Now you are locked into t...
Would you choose ServiceNow over Microsoft PowerApps?
Hi Netanya, I will choose ServiceNow because ServiceNow is a very good tool compared to Microsoft PowerApp. Because ...
What do you like most about ServiceNow?
The solution has a user-friendly interface.
Ask a question
Earn 20 points
 

Also Known As

JIRA Service Desk, Atlassian Jira Service Management
No data available
xMatters IT Management
 

Overview

 

Sample Customers

mgm technology partners, Telestream, Build.com, Zend Technologies, OfficeDrop, PGS Software, American Diabetes Association, NEPTUNE Canada
AAA, AstraZeneca, Becton, Dickinson and Company, Broadcom, Christus Health, Epicor, Equinix, GE Capital, Intuit, KPMG, Loyola Marymount University, OshKosh, Quantas, RedHat, Royal Bank of Scotland, Swiss Re, U.S. Department of Energy, Safeway, Yale University, and Zillow    
Over 2.7 million users trust xMatters daily at successful startups and global giants including athenahealth, BMC Software, Box, Credit Suisse, Danske Bank, Experian, NVIDIA, ViaSat and Vodafone. xMatters is headquartered in San Ramon, California and has offices worldwide.  Visit our website to see how business like yours found solutions with xMatters.
Find out what your peers are saying about ServiceNow, Atlassian, ManageEngine and others in IT Service Management (ITSM). Updated: March 2026.
885,789 professionals have used our research since 2012.