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

JIRA Service Management vs N-able MSP Manager 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.0
Number of Reviews
87
Ranking in other categories
No ranking in other categories
N-able MSP Manager
Ranking in Help Desk Software
28th
Ranking in IT Service Management (ITSM)
30th
Average Rating
8.4
Reviews Sentiment
7.4
Number of Reviews
4
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of October 2025, in the Help Desk Software category, the mindshare of JIRA Service Management is 7.4%, down from 11.4% compared to the previous year. The mindshare of N-able MSP Manager is 1.2%, up from 0.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Help Desk Software Market Share Distribution
ProductMarket Share (%)
JIRA Service Management7.4%
N-able MSP Manager1.2%
Other91.4%
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…
Yazan Albaw - PeerSpot reviewer
N-able MSP Manager centralizes service management, automates ticketing, and enhances client communication for streamlined IT operations.
For improvement, there's a feature I've already requested from N-able that I'd love to see in future releases. When adding a client, there should be a way to add multiple contacts under each client. Currently, we have to manually enter each contact’s details one by one, including their name, last name, password, and other information. It would be much more efficient if we could import contacts in bulk, perhaps using an Excel sheet or another import method. Additionally, it would be highly beneficial if MSP Manager could integrate with multiple RMM solutions. At the moment, we're limited to integrating with just one RMM, Expanding this capability would greatly enhance the versatility and value of MSP Manager.

Quotes from Members

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

Pros

"We have an Agile environment and using Jira makes it easy to adhere to Agile best practices."
"The dashboards are nicely laid out."
"I like the precise ticket management capabilities. JIRA Service Management is easy to use as well."
"I like the history, the dimensioning, and how I can configure a space based on my preferences or the project circumstances."
"It scales well."
"Everyone knows how to use it, so there's no need to teach new members."
"Its integration is most valuable. It is pretty open for integration."
"I think one of the most valuable things is that it's all integrated."
"I am impressed with the tool's integration with our mail system."
"I like that you can do all the things with it. You can patch, and you can run the scheduled tasks. You can remote in, upload files, and download files. You can log onto a computer PowerShell, or command prompt, without having to log into RDP. I also like its ease of use."
"The best advantage for us, since we use all N-able products, is that the MSP portal centralizes everything."
"This is a premier product and it has been around for a long time."
 

Cons

"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."
"Currently lacks an asset management module that can affect deployment."
"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."
"JIRA Service Management should make reporting easier. I would like something integrated with DevOps tools."
"Usability needs improvement. To configure it, you need to be well versed in Jira administration. It's not very intuitive."
"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."
"The reporting function of this solution, particularly the filters in the portal, could be improved."
"There is room for improvement in the user interface and the queues."
"Its reporting is lousy and bad. It is not as good as it should be. There is too much work involved to get what you want. Most times, you have to call them to customize some stuff. I just don't like that part. They need to work on their reporting. They have a way to go."
"The tool needs to improve its customization of the user interface."
"What I would like to see is a simplified solution that is packaged better, where you can easily implement or turn on the functionality that you need."
"I'd like to see a way to import contacts in bulk using an Excel sheet or another import method."
 

Pricing and Cost Advice

"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 pricing is free for us because we are an associate partner for the product."
"Licensing can become quite expensive."
"I would suggest to always buy licenses through an Atlassian partner, so you can also rely on their expertise."
"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."
"JSM's pricing is one of the best, starting at around $10 per user, per month, with volume discounts available."
"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."
"Don't get scared of the price tag because it's definitely worth it."
"I would rate the tool's pricing an eight out of ten since it's not the cheapest one in the market."
"I don't know the exact cost, but I know it's reasonable. Its cost of entry is not bad. I've had other organizations sign up for it. I don't know how much they paid, but it wasn't bad. You charge for every object. You charge for AV, and you charge for servers. There is a charge for everything or every object in that. I know we make money from it, but I don't know what it is."
report
Use our free recommendation engine to learn which Help Desk Software solutions are best for your needs.
868,706 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
17%
Financial Services Firm
10%
Manufacturing Company
8%
Educational Organization
6%
No data available
 

Company Size

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

Questions from the Community

What needs improvement with N-able MSP Manager?
For improvement, there's a feature I've already requested from N-able that I'd love to see in future releases. When adding a client, there should be a way to add multiple contacts under each client...
What is your primary use case for N-able MSP Manager?
At We Cybers, we utilize multiple N-able products, including RMM, EDR, and Passportal. N-able MSP Manager seamlessly integrates our ticketing system with both RMM Insight and N-central, enabling au...
What advice do you have for others considering N-able MSP Manager?
N-able MSP Manager also shines with its robust automation and workflow capabilities, which I find truly impressive. Users can automate the conversion of RMM triggers and alarms into tickets, automa...
 

Also Known As

JIRA Service Desk
SolarWinds LOGICnow, SolarWinds MSP Manager
 

Overview

 

Sample Customers

mgm technology partners, Telestream, Build.com, Zend Technologies, OfficeDrop, PGS Software, American Diabetes Association, NEPTUNE Canada
Longleaf Systems, ITproMedia, Choice Technology, Halski Systems, Allixo Technologies, Nettech, Concept Technology
Find out what your peers are saying about JIRA Service Management vs. N-able MSP Manager and other solutions. Updated: September 2025.
868,706 professionals have used our research since 2012.