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 (8th)
 

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 10.9%, down 12.1% compared to last year.
Splunk On-Call, on the other hand, focuses on IT Alerting and Incident Management, holds 7.1% mindshare, down 10.7% 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

"Using JIRA simplifies tracking issues and updates."
"There are two things that I value very much about this product. One is the service levels management – the SLA agreement management part of it – and knowledge management."
"It helps with time management and team management of the new tasks."
"The tool's stability is very good."
"Developing processes is easy and user-friendly."
"The customer portal allows users to register tickets themselves."
"The centralized feature allows us to track test cases and integrate with automation and bug fixing."
"What I really like about this solution, is how it manages the queues, the tickets and the routing."
"VictorOps has been good enough for us and it's effective for our needs in case of an on-call escalation process."
"The alert calling feature is the best because notifications are delivered via phone messages."
"The flexible schedule is the most valuable feature. It was very easy to set out a rotation."
"The most valuable feature of the solution is helpdesk escalation."
"Transmogrifier and automatic solution report gives me a report with the solution and the way to solve issues when an error occurred."
 

Cons

"JIRA Service could benefit from improvements to its voice support."
"The platform should be more user-friendly. JIRA's user interface needs training to understand and utilize."
"There is no notification regarding language upgrades."
"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."
"JIRA Service Management could improve the forms. When you complete the form for the ticket, for example, to have more information given to the team. If they needed this information, you can give it to them. They need to add additional information for a better understanding of the whole picture of the issue or problem."
"There is room for improvement in the user interface and the queues."
"The solution needs to be integrated better with Office X5."
"Field addition and removal features are not very intuitive in JIRA Service Management."
"The solution can be improved by including a wider list of permissions."
"Should have more YouTube webinars."
"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 third-party configuration tool could be easier to use."
"There could be improvements with communicating an incident or alert."
 

Pricing and Cost Advice

"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."
"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."
"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."
"It is one of the premium products on the market, but it is very costly, especially in the Indian market."
"On a scale of one to five, where five is a good price and one is high, I would rate this solution as a three. It isn't cheap but it's not ridiculous."
"The pricing is free for us because we are an associate partner for the product."
"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."
"For the people like us, the lower the price, the better. But when compared to other competitors, I think it's Jira's price is okay."
"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.
837,501 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
28%
Financial Services Firm
14%
Manufacturing Company
10%
Government
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about VictorOps?
The flexible schedule is the most valuable feature. It was very easy to set out a rotation.
What needs improvement with VictorOps?
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 ...
What is your primary use case for VictorOps?
We used it for on-call rotations. We used it to send alerts for monitoring. We also used it for escalation, so when we actually had an issue, it would find out who to call and call that person. It'...
 

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, ManageEngine and others in IT Service Management (ITSM). Updated: February 2025.
837,501 professionals have used our research since 2012.