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

JIRA Service Management vs ServiceNow vs Teamwork 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) Market Share Distribution
ProductMarket Share (%)
JIRA Service Management8.3%
ServiceNow19.6%
BMC Helix ITSM7.5%
Other64.6%
IT Service Management (ITSM)
IT Service Management (ITSM) Market Share Distribution
ProductMarket Share (%)
ServiceNow19.6%
JIRA Service Management8.3%
BMC Helix ITSM7.5%
Other64.6%
IT Service Management (ITSM)
Project Management Software Market Share Distribution
ProductMarket Share (%)
Teamwork1.3%
monday.com6.9%
Jira6.3%
Other85.5%
Project Management Software
 

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…
Anil  Rao - PeerSpot reviewer
Have reduced L1 dependency and improved incident resolution through AI-powered automation
To make ServiceNow better, they should reduce their pricing, especially because there's a lot of competition. Many customers have moved to ManageEngine because they cannot afford the license cost. The price should be reduced by at least 40%. The setup of ServiceNow is sometimes complex when new updates or versions are released. When they introduce something new, they should provide training to understand the new features and their functionality. We sometimes get stuck and have to call them to learn about the changes in the latest version. They should communicate the changes made from older versions to new versions, which features are not available, which features have changed, and how to implement them. If the communication part was handled properly, it would benefit us.
Ryan Beckstead - PeerSpot reviewer
A project management tool that helps to manage milestones and dependencies
We use the product to design online courses. It also helps us with media production and marketing.  Teamwork has made process management easier and much better. It is very robust and improves by making a lot of changes. It is easy to use and has lots of reports. The product is expensive. It needs…

Quotes from Members

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

Pros

"The centralized feature allows us to track test cases and integrate with automation and bug fixing."
"The initial setup is straightforward."
"​Allows customized processes for our service contracts."
"I like the precise ticket management capabilities. JIRA Service Management is easy to use as well."
"Jira gets the basics right in terms of the product backlog and a scrum board teams can use to manage sprint backlogs."
"This service management solution has a good user interface. It helps improve your IT request requirements and makes tracking requests easier."
"The query language and the ability to create views of the data are very useful."
"Compared to other solutions, Jira Service Management is really reasonable regarding price and speed."
"I have seen ROI from ServiceNow, as the client I mentioned earlier is achieving ROI for adopting this cloud-based technology."
"ServiceNow is a cloud solution. That fact was very important for us, that it is not an on-prem solution, as it reduces our internal cost of support."
"It has an excellent capability to integrate different access points."
"There are features included in the new release for intelligent software, like the chatbot. For HR services, the HR agent which is in that chatbot has been fantastic."
"ServiceNow is very easy to set up."
"What I like the most is that it's a common service data model and the fact that everything is available on one platform."
"Overall, I rate ServiceNow 10 out of 10."
"It's great to do statuses or to review tasks."
"The setup was very easy. Deployment was very fast for us. We started using it within two weeks."
"Teamwork has made process management easier and much better. It is very robust and improves by making a lot of changes. It is easy to use and has lots of reports."
"It is a very stable solution...The initial setup of Teamwork is easy."
 

Cons

"The documentation needs improving, it's difficult to find specific procedures."
"Lacks an interface where the customer can report issues."
"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."
"If I need a new feature, JIRA requires me to pay for all users when only specific people use that add-on. I should not have to pay for everyone, so this is an area for improvement."
"The platform should be more user-friendly. JIRA's user interface needs training to understand and utilize."
"The product does not have the capability to sort queued tickets by product. This would be useful in making workflows more efficient."
"When you raise a ticket with Jira, there's no ability to see your other JIRA tickets."
"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."
"It is annoying that ServiceNow keeps on changing back to Quebec every six months."
"It's a great platform, but there's still room for improvement. As the solutions stands now, you do need a lot of previous experience to use it. It would be great if they could develop some use case templates. This would be beneficial for a small and medium-sized businesses."
"Their GUI could be updated."
"The contract module is quite rudimentary and doesn't support contract line items."
"There is a need to enhance ticket details visibility on the portal, such as displaying SLA information, which currently requires development effort."
"I find ServiceNow to be a little bit clunky. If I need to report an issue they have a number of different options. I can report an issue, I can ask a question, I can make a request and it has varying levels of importance or levels of attention required. I find that what's required to submit is not always clear."
"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."
"Creating service catalog forms could be made easier."
"The product could be improved with more integrations and a mobile app."
"The product is expensive. It needs to have a more robust and customizable calendar."
"The screen sharing provided by the solution can be a challenge to a user. Screen sharing is an area that needs improvement in the solution."
 

Pricing and Cost Advice

"Actually in Iran we don't have copyright or intellectual property, so we can use JIRA for free."
"JIRA Service Desk has different pricing as it is based on agents. On average, the price is about $300 per agent."
"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."
"I would suggest to always buy licenses through an Atlassian partner, so you can also rely on their expertise."
"It's not really expensive, especially when you compare to ServiceNow or other solutions, and it's not expensive to maintain."
"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."
"Costs are about $50 per user per year. JIRA is sold in user tiers of 25, 50, 100, 250, 500, 2000, 10,000, and unlimited users. It is bad when you have 51 users then the price is based on that 100 user tier. Users at 100 will be the most cost effective."
"The cost is quite high."
"The price of the solution is comparable to industry standards. For the features that we received, it is reasonable."
"Isn't pricing always too much? We really do chafe at the ITIL licensing. ITOM is also pretty expensive."
"I have found the solution very expensive."
"ServiceNow is a leader and its pricing is quite good, quite competitive... Sometimes some plugins are not priced reasonably but, generally, the platform itself, its modules, are priced reasonably."
"The mandatory minimum is US$ 20,000 for licensing."
"The setup cost is high compared to others, especially when the scope is not fixed."
"There are licensing fees."
"We negotiate on pricing since we are a long-term user."
"My company makes annual payments towards the licensing costs of the solution."
report
Use our free recommendation engine to learn which IT Service Management (ITSM) solutions are best for your needs.
872,846 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
16%
Financial Services Firm
9%
Manufacturing Company
9%
Educational Organization
6%
Computer Software Company
12%
Financial Services Firm
12%
Manufacturing Company
10%
Government
9%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business30
Midsize Enterprise23
Large Enterprise33
By reviewers
Company SizeCount
Small Business54
Midsize Enterprise36
Large Enterprise164
No data available
 

Questions from the Community

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.
What do you like most about Teamwork Projects?
Teamwork has made process management easier and much better. It is very robust and improves by making a lot of change...
What needs improvement with Teamwork Projects?
The product is expensive. It needs to have a more robust and customizable calendar.
What is your primary use case for Teamwork Projects?
We use the product to design online courses. It also helps us with media production and marketing.
 

Also Known As

JIRA Service Desk
No data available
No data available
 

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    
PayPal, eBay, Disney, Forbes, Microsoft studios, Spotify Vevo, Lenovo, HP, Honda
Find out what your peers are saying about ServiceNow, Atlassian, BMC Helix and others in IT Service Management (ITSM). Updated: October 2025.
872,846 professionals have used our research since 2012.