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

JIRA Service Management vs Samanage comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Nov 3, 2024

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
Ranking in Help Desk Software
2nd
Ranking in IT Service Management (ITSM)
2nd
Average Rating
8.2
Reviews Sentiment
7.1
Number of Reviews
86
Ranking in other categories
No ranking in other categories
Samanage
Ranking in Help Desk Software
22nd
Ranking in IT Service Management (ITSM)
20th
Average Rating
7.6
Reviews Sentiment
6.8
Number of Reviews
3
Ranking in other categories
IT Asset Management (14th), License Management (11th)
 

Mindshare comparison

As of March 2025, in the Help Desk Software category, the mindshare of JIRA Service Management is 10.2%, down from 12.3% compared to the previous year. The mindshare of Samanage is 1.0%, up from 0.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Help Desk 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…
Moldir Shynggys - PeerSpot reviewer
Great filtering feature and a good analytics dashboard
Samanage is our ticketing system and users email us with their issues which we're then able to prioritize. We are customers of Samanage The best feature of Samanage is filtering. It also allows us to create a solution for recurring issues. It's like having a stack overflow in the company. I like…

Quotes from Members

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

Pros

"The SLA, speed, the comments from agents' side, and the dashboard for agents are the most valuable features."
"The centralized feature allows us to track test cases and integrate with automation and bug fixing."
"Everyone knows how to use it, so there's no need to teach new members."
"The most valuable feature of JIRA Service Management is a plugin we are using for the front end for simple user forms."
"Great to be able to create customized forms."
"Easily integrates with other tools."
"The links between the help desk and Jira issues and between Confluence and Jira issues are most valuable. I can write requirements in Confluence and link them to user stories in Jira and test cases. I can see my test coverage and all that kind of stuff. The integration between these three is very useful. It is pretty customizable, and it integrates well. There are a lot of add-ins and a lot of connectors to third-party products. In my last company, we used Test Royal for managing all the tests, and it integrated perfectly with that. For any issue or bug, we could see what tests have been run and the complete history of the tests."
"The dashboards are nicely laid out."
"The best part is the ability to keep records, especially incident records. It's easy to use the tool to store data and monitor it."
"The solution has a great filtering feature."
 

Cons

"The licensing model could be improved."
"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."
"JIRA Service could benefit from improvements to its voice support."
"There should be some AI integrations now as AI is in the picture."
"It is pretty complex to move between the test environment and the production environment. There is potential for improvement."
"Cost has prohibited us from switching entirely to this solution."
"The product does not have the capability to sort queued tickets by product. This would be useful in making workflows more efficient."
"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 setting up process is not quite easy. It's quite difficult."
"The system shuts down about once a month which is frustrating."
 

Pricing and Cost Advice

"The cost has recently increased. It might be around $20 to $25 per user license."
"The price of the solution is becoming expensive and it should be reduced."
"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."
"Actually in Iran we don't have copyright or intellectual property, so we can use JIRA for free."
"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 costs around $150 to $200 per user."
"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."
"It is expensive."
report
Use our free recommendation engine to learn which Help Desk Software solutions are best for your needs.
842,651 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
7%
Construction Company
14%
Manufacturing Company
10%
Computer Software Company
8%
Financial Services Firm
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What do you like most about Samanage?
The best part is the ability to keep records, especially incident records. It's easy to use the tool to store data and monitor it.
What needs improvement with Samanage?
We mainly use it for incident logging. We'd like to add service request functionality, but we don't have the knowledge to configure the requests and the workflows properly. We'd like to integrate o...
What is your primary use case for Samanage?
I use it for incident recording based on your inventory.
 

Also Known As

JIRA Service Desk
No data available
 

Overview

 

Sample Customers

mgm technology partners, Telestream, Build.com, Zend Technologies, OfficeDrop, PGS Software, American Diabetes Association, NEPTUNE Canada
SXSW, PRA Group, Fandango, Inteva Products, Amherst College, Tensator
Find out what your peers are saying about JIRA Service Management vs. Samanage and other solutions. Updated: February 2025.
842,651 professionals have used our research since 2012.