No more typing reviews! Try our Samantha, our new voice AI agent.

JIRA Service Management vs Moveworks 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
6.8
Number of Reviews
90
Ranking in other categories
Help Desk Software (2nd), IT Service Management (ITSM) (2nd)
Moveworks
Average Rating
8.4
Reviews Sentiment
6.0
Number of Reviews
3
Ranking in other categories
AI-Powered Chatbots (2nd), Agentic Automation (7th), AI-Agents for HR (3rd)
 

Mindshare comparison

JIRA Service Management and Moveworks aren’t in the same category and serve different purposes. JIRA Service Management is designed for IT Service Management (ITSM) and holds a mindshare of 6.9%, down 9.8% compared to last year.
Moveworks, on the other hand, focuses on Agentic Automation, holds 3.2% mindshare, up 0.4% since last year.
IT Service Management (ITSM) Mindshare Distribution
ProductMindshare (%)
JIRA Service Management6.9%
ServiceNow14.2%
BMC Helix ITSM5.5%
Other73.4%
IT Service Management (ITSM)
Agentic Automation Mindshare Distribution
ProductMindshare (%)
Moveworks3.2%
UiPath Platform20.5%
Microsoft Power Automate18.3%
Other58.0%
Agentic Automation
 

Featured Reviews

Sohaib Ahmad - PeerSpot reviewer
Vice President Service Delivery at quixel
Comprehensive workflows and data views have supported complex teams but still need cost improvements
JIRA Service Management is costly. The pricing structure needs improvement. When I add some plugins, I have to pay the cost for every user whether they are using it or not. For smaller companies, the detailed workflow editing and the kind of details that JIRA Service Management provides would be complex. For startups and smaller companies, JIRA Service Management would be complex. The cloud offering is easier because I don't have to manage the infrastructure. There are two templates of the project: company-managed and team-managed. Team-managed is a newer feature, which is good for startup-kind companies where they don't need control over data from multiple projects displaying in one dashboard. For startups, JIRA Service Management is somewhat complex with its schemes and everything. Capacity management should be improved in terms of additional features in the next release of JIRA Service Management.
reviewer2800146 - PeerSpot reviewer
Software Developer at a consultancy with 51-200 employees
Chat-based requests have streamlined daily workflows
Moveworks can definitely be improved. Currently, we have to do most of the things on our own, such as creating UI and APIs for how things will work. There are not many things that Moveworks is supporting right now. I would say it should have some features that are already present in other bots, so they should focus on those more. Currently, Moveworks has UI policy restrictions and client script restrictions. I think they should edit it so that all these UI policies and other things are allowed. If there are some forms in Moveworks, it should capture that form and ask it in the chat from the user, taking answers one by one, rather than presenting a form to users. This would have a very positive impact.

Quotes from Members

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

Pros

"Jira Service Management has a workflow feature you can configure for your specific requirements. It also lets you efficiently manage service requests with team members."
"JIRA SD also helps for much better feedback on the work being done. All colleagues can see what is happening."
"It is much more controlled and allows for different kinds of customization that we can plan and implement based on the project requirements."
"Everyone knows how to use it, so there's no need to teach new members."
"The customer portal with connection with our knowledge base has been most valuable."
"The solution is easy, even if you want to dock on something, it's easy to add the documentation and it easily integrates with other tools."
"The basic configuration and the basic abilities provided are the most valuable aspects of the solution."
"Customizations are most valuable. The customization of workflows is the main power of the Atlassian tools in general."
"Moveworks is a very good platform if you utilize it well."
"Moveworks has reduced employee time because initially, employees used to spend so much time going to the third party to do all those jobs, and now they can simply do it via Otter, which is Moveworks, and this has saved much time and provided accurate results as well."
"The solution saves us approximately three-quarters of a million dollars per year."
 

Cons

"The price is a point of contention for me. It does overall work out as a significant amount of money that will be spent over a shorter period of time."
"In the Turkish market, the biggest problem is that they are looking for a server type of solution, but when it comes to Jira Service Management, Atlassian is a remote type of license. There are just two different options, data center and cloud."
"In general, JIRA has no relation to customers or financials. Therefore, marketplace add-ons are needed to make it work for customer-facing systems."
"The cost of the license is too high; it's a real challenge for companies that aren't already using JIRA products."
"There is room for improvement in the user interface and the queues."
"It has change management and incident management, but CMDB is not there. It's also not as user-friendly as ServiceNow."
"It does not integrate very well with our email system (MS Outlook)."
"​SaaS version for large organizations (more than 2000 users) is not available."
"Moveworks can definitely be improved. Currently, we have to do most of the things on our own, such as creating UI and APIs for how things will work."
"More use cases can be added to the agent marketplace and the YAML or the DSL methods can be simplified, adding more methods to make it easier for us to create compound actions."
 

Pricing and Cost Advice

"We need a license because we have a higher number than the free part."
"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."
"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."
"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."
"I am using the free version, but my clients are paying for it. When they start, they evaluate it for 30 days, and after seeing the value, they move to its paid version."
"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 may upgrade the license that we have. The license that we currently have is good for 500 agents, and it's not full yet."
Information not available
report
Use our free recommendation engine to learn which IT Service Management (ITSM) solutions are best for your needs.
894,807 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
14%
Manufacturing Company
9%
Computer Software Company
6%
Educational Organization
6%
Manufacturing Company
13%
Financial Services Firm
11%
Comms Service Provider
7%
Media Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business30
Midsize Enterprise25
Large Enterprise34
No data available
 

Questions from the Community

What is your experience regarding pricing and costs for JIRA Service Management?
While licensing is costly, setting up JIRA Service Management is overall good because the vendor helped me, and I also received support from JIRA support, making it a positive experience.
What needs improvement with JIRA Service Management?
I feel JIRA Service Management could be better if the APIs from the sponsoring team provided more support and flexibility in API endpoints. Regarding JIRA Service Management's API and support, the ...
What needs improvement with Moveworks?
Moveworks can definitely be improved. Currently, we have to do most of the things on our own, such as creating UI and APIs for how things will work. There are not many things that Moveworks is supp...
What is your primary use case for Moveworks?
I am currently working in ServiceNow at Symbiotic Consulting Group as a software developer. I have been using Moveworks for two years now. We have ServiceNow integrations with Moveworks, such as fi...
What advice do you have for others considering Moveworks?
Most of the things I have already discussed about the features, but the unexpected thing was creating paths on our own. Before using Moveworks, it used to take almost three to four minutes for a pe...
 

Also Known As

JIRA Service Desk, Atlassian Jira Service Management
No data available
 

Overview

 

Sample Customers

mgm technology partners, Telestream, Build.com, Zend Technologies, OfficeDrop, PGS Software, American Diabetes Association, NEPTUNE Canada
slack, equinix, appdynamics, nutanix, broadcom, autodesk, medallia, freedom
Find out what your peers are saying about ServiceNow, Atlassian, ManageEngine and others in IT Service Management (ITSM). Updated: May 2026.
894,807 professionals have used our research since 2012.