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

IBM SmartCloud Control Desk vs JIRA Service Management vs ServiceNow 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

As of April 2026, in the Help Desk Software category, the mindshare of IBM SmartCloud Control Desk is 1.1%, up from 0.6% compared to the previous year. The mindshare of JIRA Service Management is 6.1%, down from 9.3% compared to the previous year. The mindshare of ServiceNow is 11.7%, down from 23.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Help Desk Software Mindshare Distribution
ProductMindshare (%)
ServiceNow11.7%
JIRA Service Management6.1%
IBM SmartCloud Control Desk1.1%
Other81.1%
Help Desk Software
 

Featured Reviews

KM
Computer System Engineer at Informatika d.d.
Has centralization and asset management features, and a helpful and knowledgeable technical support team
What needs improvement in IBM SmartCloud Control Desk is its graphical interface because it needs to be more user-friendly. IBM is a big company, but this solution is a little bit outdated. The most common comment I get from customers is that IBM SmartCloud Control Desk looks old and needs a refresh. Its frontend needs a little bit of work. The solution needs to be more modern. In the programming world, you see a lot of new technologies, but this particular solution is still on Java. IBM SmartCloud Control Desk isn't like web-based service request tools, and that's an area for improvement. What I'd like to see in the next version of the solution is a more upscale technology. IBM SmartCloud Control Desk has small issues with document links and attachments, and those could bother you when you're using it for a long time. A more user-friendly GUI is also another improvement I'd like to see in the next version of the solution, plus a better user experience, and it would be great if IBM could resolve the current issues I've noticed in IBM SmartCloud Control Desk.
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.
Hemanthreddy Vakiti - PeerSpot reviewer
Data engineer at a tech vendor with 10,001+ employees
Structured workflows have improved SLA compliance and now support prioritized incident handling
I think the licensing and pricing of ServiceNow is quite expensive compared to other tools. For large organizations, it is acceptable, but specifically for small and medium organizations to track incidents or change requests, ServiceNow is quite expensive. Sometimes performance can be slow when workflows and integrations are configured for complex tasks. For advanced customizations or advanced features which we rarely use, the documentation is not up to standard. The documentation needs to be improved for advanced customization features. However, the platform is stable overall and the features are quite good. The user experience and performance concerns I mentioned are areas I want to be improved. When many workflows and interactions are configured, performance is slow. For the features it is providing, it is quite expensive. If these performance features are improved, we can easily pay that price and get the return on investment.

Quotes from Members

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

Pros

"What I like about the Control Desk is that everything is centralized, you have all the requests in one place, you know which ones are for whom and who is working on them, so you have one big package and nothing is lost."
"The most valuable are its flexibility and agility. It's quick to change it, to adapt it to your needs. That's the most important for us."
"The solution has been stable."
"SLA integrations, reports, and integration with other applications are the most valuable."
"The brand name is the most valuable aspect of this solution for me; it's IBM, a global company that supports this product, not something open source or something like that."
"The solution is very easy to work with."
"The workflow capability is useful. It's not a manual helpdesk operation. It's fully automated, even when an alarm has occurred. It covers the complete cycle of initiation to resolving the events. This is its most strong feature that is easily integrable with a monitoring solution. It creates tickets, and the workflow feature is the most important one."
"Overall, it has helped us continuously improve our business processes."
"Customizations are most valuable. The customization of workflows is the main power of the Atlassian tools in general."
"I think that people should really go for it because of its ease of use."
"I'm mainly working in the ITSM module of JIRA Service Management, and the integration between the system incident and how you can link all the records to the change makes it quite powerful."
"This is the most complete and versatile enterprise task management product and issue tracker."
"The solution is scalable; we have currently deployed it to about 35 agents and it will be deployed to around 1200 customers, all of them dealing with creating and resolving tickets."
"Automation capabilities allow for automatic ticket creation using monitoring tools."
"Jira is becoming quite popular and is well supported."
"It helps with time management and team management of the new tasks."
"Overall it's a great product."
"It helped me save time—it would be more than 30% in time savings, with fewer man-hours and improved service delivery through automation capabilities."
"The product scales wonderful, we don't have to worry about the scalability and someplace else, and I wouldn't say there are any issues with the product right now from the performance and scalability point of view; it's been performing very well."
"Data in reports and dashboards are easily accessible."
"Everything about the schema, including the design of ServiceNow, is great."
"ServiceNow is the best ticketing tool I have used so far."
"The product is extremely stable, with no bugs or glitches, and it doesn't crash or freeze, making it very reliable and not problematic at all."
"You can scale the solution."
 

Cons

"Support has been the biggest problem for us."
"It could use more facility or flexibility for reporting, and business intelligence in the tool."
"Technical support can be slow in terms of resolving issues."
"Overall the user experience, as opposed to the system and databases, could be improved. It does work as it should and it's good, but they should invest more in the user interfaces to be less data oriented and more appealing for the user."
"Their technical support can also be improved in terms of response time."
"The main issue that we hear from our customers is that the self-service user interface is a little bit old, possibly due to the fact that IBM is such a large enterprise company."
"The user interface is not very interesting."
"It could use more facility or flexibility for reporting, and business intelligence in the tool."
"The initial setup of JIRA Service Management can be complex for new users. There is a lot of configuration."
"It was complex for us because we had to migrate data from HPSM. We required a consultant to be involved, and even the consultant struggled for some time."
"The licensing model could be improved. There needs to be a different licensing model for large numbers of employees, as it remains one of the main barriers to using JIRA Service Management across our entire company."
"It does not integrate very well with our email system (MS Outlook)."
"The initial setup is very complex."
"For us, one of the weaknesses of Service Desk is that we can not check every issue in the queue raised for one product."
"Integration could be improved."
"From the customer side, it's not friendly used compared to other competitors, like ServiceNow or BMC."
"We do a lot of relatively advanced stuff for the size that we are, but ServiceNow itself is so big and to some extent, there is a significant amount of complexity that you have, a big learning curve I would say, in order to really get on board."
"Transparency in the pricing model needs to be improved."
"We have implemented some various complex ACLs and they've impacted our performance significantly, and we've had several incidents open to help with performance, and it's been kind of a struggle to get the ServiceNow support group to say "Yup, I see it's a problem, let's do this.""
"It became kind of complex to set it up without a general lack of knowledge of the particular feature-function capabilities."
"Before implementing this solution, you should have the ITSM model in place for change management requests. That is a prerequisite because you cannot perform tasks without it."
"I think they also should rethink the way they license the tool because it’s too expensive to automate all of your business, but you’ll need lots of licenses."
"Before implementing this solution, you should have the ITSM model in place for chain management requests. That is a prerequisite because you cannot perform tasks without it."
"Performance could be improved."
 

Pricing and Cost Advice

"It's basically for a big company because of the costs. A small company can't afford the licensing cost. For medium and large companies, it's the best product. The price of the license is on the higher side compared to others."
"The licensing we have for IBM Control Desk is on a yearly basis. They have a concurrent license and an administrative license. And with these, you get all the products. There aren't any additional fees for extra add-ons or anything like that."
"The license for IBM SmartCloud Control Desk is paid yearly and is on a per-user basis. You buy the product and pay for its license yearly. IBM is changing the licensing structure, but for now, it's a yearly license. There's no additional cost. It's just the license that you need to pay for to use IBM SmartCloud Control Desk."
"On a scale of one to five, with one being really high and five being good, I would rate the price of this solution as a four."
"We need a license because we have a higher number than the free part."
"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."
"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."
"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."
"I price of JIRA Service Management is reasonable."
"JSM's pricing is one of the best, starting at around $10 per user, per month, with volume discounts available."
"The price is okay for us. It's reasonable."
"The product cost is higher than that of other vendors."
"There are licensing fees."
"The price could be a little lower for the solution. Many of my customers have issues with the licensing process, they have to make it easier and straightforward."
"The mandatory minimum is US$ 20,000 for licensing."
"It is very expensive because it is a big organization. You have to pay for additional things."
"The first impact for the customer is that it is expensive, but do not forget that it is a solution that includes infrastructure; a single cost, easy to justify."
"The solution is expensive."
report
Use our free recommendation engine to learn which Help Desk Software solutions are best for your needs.
892,287 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Performing Arts
18%
Comms Service Provider
12%
Construction Company
12%
Manufacturing Company
6%
Financial Services Firm
14%
Manufacturing Company
9%
Computer Software Company
7%
Educational Organization
6%
Financial Services Firm
12%
Manufacturing Company
10%
Government
8%
Computer Software Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business6
Large Enterprise3
By reviewers
Company SizeCount
Small Business30
Midsize Enterprise25
Large Enterprise34
By reviewers
Company SizeCount
Small Business55
Midsize Enterprise35
Large Enterprise171
 

Questions from the Community

Ask a question
Earn 20 points
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 flexibi...
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.
 

Also Known As

SmartCloud Control Desk
JIRA Service Desk, Atlassian Jira Service Management
No data available
 

Overview

 

Sample Customers

St Vincent's Health Australia, Kalibrate Pty. Ltd., Cognizant Technology
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    
Find out what your peers are saying about ServiceNow, Atlassian, ManageEngine and others in Help Desk Software. Updated: April 2026.
892,287 professionals have used our research since 2012.