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

Hornbill Systems Supportworks vs JIRA Service Management comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 29, 2025

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

Hornbill Systems Supportworks
Ranking in Help Desk Software
36th
Ranking in IT Service Management (ITSM)
36th
Average Rating
7.0
Reviews Sentiment
6.8
Number of Reviews
2
Ranking in other categories
No ranking in other categories
JIRA Service Management
Ranking in Help Desk Software
2nd
Ranking in IT Service Management (ITSM)
2nd
Average Rating
8.2
Reviews Sentiment
6.8
Number of Reviews
88
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of February 2026, in the IT Service Management (ITSM) category, the mindshare of Hornbill Systems Supportworks is 1.0%, up from 0.6% compared to the previous year. The mindshare of JIRA Service Management is 7.3%, down from 11.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
IT Service Management (ITSM) Market Share Distribution
ProductMarket Share (%)
JIRA Service Management7.3%
Hornbill Systems Supportworks1.0%
Other91.7%
IT Service Management (ITSM)
 

Featured Reviews

it_user1262703 - PeerSpot reviewer
Service Desk Team Leader at a healthcare company with 5,001-10,000 employees
Excels in call logging and call flows but is limited in terms of scalability
I'd advise others to map their processes out before starting with the solution. Hornbill has recently generated a new version of its product and it meets some of the requirements that we would have been looking for. It's a bit more scalable, a bit more responsive to a customer-focused model for support, and they've improved a lot of things like process flow and self-service. In terms of rating the solution, it's difficult to grade. It really depends on the size of the organization that's trying to use it as that tool. One of the reasons why we're looking to shift is because we've grown quite a bit over the years that we've had it, which makes it difficult for it to meet our demands. However, for an organization the size of what we were when we started our journey with it, I'd rate it ten out of ten. Where we are now, with our company size and needs, I'd rate it six out of ten.
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.

Quotes from Members

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

Pros

"The solution's business process flow is quite strong. Its reporting is quite good. The standard, basic ITSM functionality like call logging and call flow, for example, are areas the solution really excels in."
"The dashboards are nicely laid out."
"The SLA, speed, the comments from agents' side, and the dashboard for agents are the most valuable features."
"The tool's stability is very good."
"I like the precise ticket management capabilities. JIRA Service Management is easy to use as well."
"The most valuable features of JIRA Service Management are the service level agreement or management, and the ticketing system. Additionally, there are frequent updates that provide improvements."
"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."
"Everyone knows how to use it, so there's no need to teach new members."
"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."
 

Cons

"It's worked well for us for a significant period of time. However, we are kind-of outgrowing it at the moment. We're struggling a bit with making it meet our requirements."
"The deployment can be a bit complex, especially for those who are not technical."
"I am not familiar if there's an integration with Visual Studio from Jira."
"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."
"​SaaS version for large organizations (more than 2000 users) is not available."
"Currently lacks an asset management module that can affect deployment."
"The search function could be improved. We have to search a certain way. There is no generic search; it is more object-oriented search."
"The licensing model could be improved."
"Integration could be improved."
 

Pricing and Cost Advice

"Our organization pays about $40,000 annually. There are ongoing consultancy costs and if we want to change anything, we're charged a day rate. Other than that, there are no other extra costs involved in working with the solution."
"It is one of the premium products on the market, but it is very costly, especially in the Indian market."
"Licensing can become quite expensive."
"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."
"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."
"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."
"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."
"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."
report
Use our free recommendation engine to learn which IT Service Management (ITSM) solutions are best for your needs.
881,565 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Computer Software Company
9%
Financial Services Firm
9%
Manufacturing Company
9%
Educational Organization
7%
 

Company Size

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

Also Known As

Supportworks
JIRA Service Desk, Atlassian Jira Service Management
 

Overview

 

Sample Customers

Aylesbury Vale District Council
mgm technology partners, Telestream, Build.com, Zend Technologies, OfficeDrop, PGS Software, American Diabetes Association, NEPTUNE Canada
Find out what your peers are saying about Hornbill Systems Supportworks vs. JIRA Service Management and other solutions. Updated: January 2026.
881,565 professionals have used our research since 2012.