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

"The most valuable feature of JIRA Service Management is a plugin we are using for the front end for simple user forms."
"The most valuable features of JIRA Service Management are the service level agreement or management, and the ticketing system. Additionally, there are frequent updates that provide improvements."
"The solution offers lots of information on the website to assist with technical queries. There are also many community sites to help you troubleshoot any problems."
"The product is not lacking anything that a QA will want to use."
"The most valuable feature of the solution is its SLA, which everybody wants when it comes to a service-based offering."
"It makes the IT department more transparent and helps the employees."
"With Jira Service Desk, the simplicity of setting up a quick form and getting the service desk running quickly is very helpful."
"The visibility features are great."
"The alert calling feature is the best because notifications are delivered via phone messages."
"Transmogrifier and automatic solution report gives me a report with the solution and the way to solve issues when an error occurred."
"The most valuable feature of the solution is helpdesk escalation."
"The flexible schedule is the most valuable feature. It was very easy to set out a rotation."
"VictorOps has been good enough for us and it's effective for our needs in case of an on-call escalation process."
 

Cons

"Initially, as a completely new user, the interface was not very user-friendly, with many cluttered options."
"I rate Atlassian support two out of 10. It takes a lot of time to reach them and get ahold of someone who understands my problem enough to provide a solution. Also, I live in Israel, so my work week is Sunday through Thursday, but I can only contact them from Monday to Wednesday."
"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 we can have an easier way to deploy this solution without the help of a consultant and a more reliable way of deploying procedures, it would be quite helpful."
"Include a split configuration in a layer part to allow cloud services to have almost full admin rights in SaaS."
"In-built chat is missing in JIRA Service Management."
"Field addition and removal features are not very intuitive in JIRA Service Management."
"JSD has some analytics, but it's pretty much basic and simple dashboards. There's no mobile application for JSD. It really would benefit from better implementation with other vendors. We're heavily reliant on some external marketplace applications."
"Should have more YouTube webinars."
"There could be improvements with communicating an incident or alert."
"The third-party configuration tool could be easier to use."
"At that stage, all our needs are fulfilled, but at the beginning, we had some feature requests and they were deployed during their roadmap."
"The solution can be improved by including a wider list of permissions."
 

Pricing and Cost Advice

"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."
"It is one of the premium products on the market, but it is very costly, especially in the Indian market."
"I price of JIRA Service Management is reasonable."
"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."
"We have an annual license with JIRA Service Management, but it is billed monthly."
"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."
"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."
"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 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.
860,168 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.
860,168 professionals have used our research since 2012.