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

JIRA Service Management vs Splunk On-Call 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)
Splunk On-Call
Average Rating
8.6
Reviews Sentiment
6.9
Number of Reviews
10
Ranking in other categories
IT Alerting and Incident Management (12th)
 

Mindshare comparison

While both are Systems Management solutions, they serve different purposes. JIRA Service Management is designed for IT Service Management (ITSM) and holds a mindshare of 9.1%, down 12.0% compared to last year.
Splunk On-Call, on the other hand, focuses on IT Alerting and Incident Management, holds 4.3% mindshare, down 9.4% since last year.
IT Service Management (ITSM)
IT Alerting and Incident Management
 

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…
Wojtek Witowski - PeerSpot reviewer
Allows us to create flexible schedules for on-call rotations
For alerts, we could choose to get a text message, app notification, or a phone call. The phone calls were very unusable, because it just read a bunch of numbers, like an ID of the alert. If there was a way to customize the phone call message, that would be great. Later, we would try to read the message, but it wasn't great at reading that. They had some sort of internal chat functionality where if we got an alert, we could write to somebody else and ask them for help, but that was super cumbersome. There could be improvements with communicating an incident or alert. Imagine you call the help desk and you say that your computer is broken and then they say, "Actually, the internet is broken, so let us forward your alerts to the network people." And the network people say, "Actually, the electricity is the problem, so let us forward it to the electricity people." Basically, you could send the alert between the support teams inside the company.

Quotes from Members

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

Pros

"It is 100% stable."
"Automation capabilities allow for automatic ticket creation using monitoring tools."
"This solution has helped us a great deal in project management tracking and forecasting."
"The centralized feature allows us to track test cases and integrate with automation and bug fixing."
"The customer portal with connection with our knowledge base has been most valuable."
"We can track, monitor, and get all the details we need from the end-user's point of view for any service request."
"What I really like about this solution, is how it manages the queues, the tickets and the routing."
"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."
"VictorOps has been good enough for us and it's effective for our needs in case of an on-call escalation process."
"Transmogrifier and automatic solution report gives me a report with the solution and the way to solve issues when an error occurred."
"The flexible schedule is the most valuable feature. It was very easy to set out a rotation."
"The alert calling feature is the best because notifications are delivered via phone messages."
"The most valuable feature of the solution is helpdesk escalation."
 

Cons

"The search function could be improved. We have to search a certain way. There is no generic search; it is more object-oriented search."
"The licensing model could be improved."
"It is pretty complex to move between the test environment and the production environment. There is potential for improvement."
"The reporting function of this solution, particularly the filters in the portal, could be improved."
"The licensing model could be improved. There needs to be a different licensing model for large numbers of employees, as it remains one of the main barriers to using JIRA Service Management across our entire company."
"An AI feature that enables automation and alerts for users can be an improvement."
"I would like to see the user interface changed, it is not very user-friendly, and it transitions workflows."
"The product does not have the capability to sort queued tickets by product. This would be useful in making workflows more efficient."
"Should have more YouTube webinars."
"The solution can be improved by including a wider list of permissions."
"At that stage, all our needs are fulfilled, but at the beginning, we had some feature requests and they were deployed during their roadmap."
"There could be improvements with communicating an incident or alert."
"The third-party configuration tool could be easier to use."
 

Pricing and Cost Advice

"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."
"We have an annual license with JIRA Service Management, but it is billed monthly."
"The price of the solution is becoming expensive and it should be reduced."
"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."
"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."
"I would suggest to always buy licenses through an Atlassian partner, so you can also rely on their expertise."
"I would rate the pricing a seven out of ten, where one is low price, and ten is high price. It's competitively priced."
"JIRA Service Desk has different pricing as it is based on agents. On average, the price is about $300 per agent."
"The price of the solution could be less expensive."
report
Use our free recommendation engine to learn which IT Service Management (ITSM) solutions are best for your needs.
859,957 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
19%
Financial Services Firm
10%
Manufacturing Company
8%
Government
6%
Computer Software Company
34%
Manufacturing Company
11%
Financial Services Firm
11%
Government
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Also Known As

JIRA Service Desk
VictorOps
 

Overview

 

Sample Customers

mgm technology partners, Telestream, Build.com, Zend Technologies, OfficeDrop, PGS Software, American Diabetes Association, NEPTUNE Canada
NVIDIA, Cisco, NBC, Rackspace, Intuit, DirectTV, NASCAR, Arrow Electronics, Alliance Health, NetApp, Edmunds, New York Times, Return Path, Sony Playstation, CA Technologies, Sphero, Symantic, HBO, Weatherford, Blackboard, Epic Games
Find out what your peers are saying about ServiceNow, Atlassian, BMC and others in IT Service Management (ITSM). Updated: June 2025.
859,957 professionals have used our research since 2012.