We performed a comparison between Jira Service Management and ServiceNow based on our users’ reviews in five categories. After reading all of the collected data, you can find our conclusion below.
Comparison Results: Because ServiceNow offers fewer features, is more expensive, and is more difficult to set up, Jira Service Management ultimately wins out in this comparison.
"It is much more controlled and allows for different kinds of customization that we can plan and implement based on the project requirements."
"The customer portal with connection with our knowledge base has been most valuable."
"Service Management is great if you're an Atlassian shop already using JIRA for the development team and you want another tool for help desk ticketing. When it's all under the same umbrella, I can easily take a ticket from the help desk and move it to the development team. You can't beat that integration between two products."
"The most valuable feature of JIRA Service Management is a plugin we are using for the front end for simple user forms."
"The customer portal allows users to register tickets themselves."
"Great to be able to create customized forms."
"We use JIRA Service Management for tracking purposes, planning, and execution."
"It has improved our work in a number of ways. First, it has made everything much faster. Before Jira Service Management, it could take weeks to resolve a ticket."
"A workflow automation platform that's reliable, performs well, and has good reporting and integration."
"It enables us to meet SLAs, track issues across the environment, and report those issues."
"It offers ready-built automation and simpler configuration for workflows."
"It has more extensive features as compared to the other competitors."
"We have found change management and CMDB to be very useful."
"The Workflow feature is the most valuable."
"Will give us better control over asset management and technical debt once we can centralize all contract information."
"I find almost all the features valuable. It can do nearly everything except make your coffee, as my colleagues always say. It's got pros and cons, like every software, but the good thing about it is that it has a very structured approach."
"The queries are weak and lack advanced functionality. You can do rudimentary queries, but you can't aggregate. You can't filter for a lot of things that would be useful, so you need to use plugins to write writing advanced queries. I run into problems when working with different organizations because they always have restrictions on what kind of plugins they allow."
"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 initial setup is very complex."
"The solution needs to be integrated better with Office X5."
"Cost has prohibited us from switching entirely to this solution."
"From the customer side, it's not friendly used compared to other competitors, like ServiceNow or BMC. It's also not fully ITSM management if you compare it with ServiceNow or BMC. They have a full model of ITSM. In BMC they have TrueSight, they have Discovery, which helps IT to discover IT equipment with a serial number, with the specs, capacity of the server."
"Lacks an interface where the customer can report issues."
"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."
"ServiceNow doesn't cater to the Middle Eastern market."
"It's a little expensive compared to other tools."
"I find the way you need to attach things like screenshots and stuff is a bit gimmicky. I'm a casual user. I'll use it once every two months and only when I have an incident that I need to report. You don't get a lot of experience with it when you're just using it once in a while like that. Therefore, it needs to be more intuitive so that you don't have to re-learn how to do simple tasks as the way to do certain things just isn't obvious."
"The pricing structure could be more budget-friendly."
"When it comes to reference fields, there are some limitations where you aren't able to use them, like in relationship queries. In Remedy, when you click a menu, you get options directly, whereas here, if you use a reference field, it points you to a different form. So the UI experience totally changes for the end user."
"Complexities in the organization made the initial deployment complex."
"Change Management is the area I have found that this tool can be improved because there are so many fields which are missing, such as urgency of the customer request and how the priority is defined. These are some of the areas in which I found that BMC Remedy is much better than ServiceNow."
"The visuals are the one area where there is opportunity for improvement."
JIRA Service Management is ranked 2nd in Help Desk Software with 73 reviews while ServiceNow is ranked 1st in Help Desk Software with 211 reviews. JIRA Service Management is rated 8.2, while ServiceNow is rated 8.4. The top reviewer of JIRA Service Management writes "Customizable, stable, and integrates well". On the other hand, the top reviewer of ServiceNow writes "A stable and scalable solution that has excellent features and is useful for collecting data and building KPIs". JIRA Service Management is most compared with ManageEngine ServiceDesk Plus, BMC Helix ITSM, Freshdesk, PagerDuty Operations Cloud and Zendesk, whereas ServiceNow is most compared with BMC Helix ITSM, Microsoft Power Apps, Pega BPM, IBM Maximo and LeanIX. See our JIRA Service Management vs. ServiceNow report.
See our list of best Help Desk Software vendors and best IT Service Management (ITSM) vendors.
We monitor all Help Desk Software reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
ServiceNow is an expensive ITSM tool and JIRA Service Desk will be good to have to development projects. Now a day organizations look for tailored solutions as per their IT needs.
If you need an ITIL aligned helpdesk system, codeless customizations and cost-effective, check out ManageEngine Servicedesk Plus.
JIRA Service Desk gives you a better monetary deal.
I don’t know the answer, but I assume JIRA will be significantly less money.
Jira Service desk supports ITIL and gives you many templates for different helpdesk scenarios, allows to creates issues using the email. The implementation of Service Desk is easy and intuitive