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

JIRA Service Management vs OrbusInfinity comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Apr 5, 2026

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 IT Service Management (ITSM)
2nd
Average Rating
8.2
Reviews Sentiment
6.8
Number of Reviews
90
Ranking in other categories
Help Desk Software (2nd)
OrbusInfinity
Ranking in IT Service Management (ITSM)
36th
Average Rating
8.0
Reviews Sentiment
7.2
Number of Reviews
2
Ranking in other categories
Enterprise Architecture Management (14th)
 

Mindshare comparison

As of May 2026, in the IT Service Management (ITSM) category, the mindshare of JIRA Service Management is 6.9%, down from 9.8% compared to the previous year. The mindshare of OrbusInfinity is 0.8%, up from 0.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
IT Service Management (ITSM) Mindshare Distribution
ProductMindshare (%)
JIRA Service Management6.9%
OrbusInfinity0.8%
Other92.3%
IT Service Management (ITSM)
 

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.
Kenneth Igiri - PeerSpot reviewer
Enterprise Architect at Ecobank Transnational Incorporated
Cost-effective, integrates with the Office tools, and allows us to articulate all entities across the enterprise on one platform
The refresh cycles for our dashboards could be better. I keep complaining about that. The refresh is supposed to be once a day, but I would love it if it was real-time so that if I make a change to the data in iServer, I should see those changes immediately reflected in the dashboards. They use Power BI, and it seems they've scheduled their refresh to be once a day, which is not that good for us. We've had some issues with the integration between Visio and iServer because sometimes the add-in that allows you to do that integration takes a lot of memory and then your Visio crashes. However, I've not experienced this issue for some time, so it was probably fixed in the recent version. Also, if I copy a large amount of data and I want to copy from one Visio file to another, I have had a case where it suddenly just closes Visio without saving. So, that integration could be more smooth. There should be ease of integration with other systems in our environment such as SysAid. I understand that there is an integration to ServiceNow, but we use SysAid. We need to be able to say that when there's an incident that impacts or requires a change in a particular component, ServiceNow or SysAid should be able to communicate to Orbus that this component is about to change. Similarly, when it comes to discovery or when a new architecture change has happened in the enterprise, we should be able to detect the change in the baseline Enterprise Architecture. There should be such advanced automation. The visibility of our models is limited to those to whom we have assigned licenses. I would've loved it if everyone in the organization could at least see the diagrams. The licensing should be there for those who need to make updates or changes.

Quotes from Members

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

Pros

"It scales well."
"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 most valuable feature of JIRA Service Management is a plugin we are using for the front end for simple user forms."
"Everyone knows how to use it, so there's no need to teach new members."
"We use JIRA Service Management for tracking purposes, planning, and execution."
"Easy to use and user-friendly."
"JIRA Service Management is user-friendly and can help you achieve what you want to achieve."
"The visibility features are great."
"The most valuable features are mainly the reporting side of things and the dashboard."
"The most valuable features are mainly the reporting side of things and the dashboard."
"I like the integration with the Office tools such as Visio and Excel. The integration with Excel helped us to be able to upload data very easily. Integration with Visio helps us to be able to make changes once and have a centralized diagram. We don't have versions of the diagram. This integration with the Office tools is very useful."
 

Cons

"The product does not allow customization of reports."
"Every time there's a problem with JIRA Service Management, you have to have a look at how to solve it, and there's always a feature request or the feature request on the solution is too large and the development cycles are too slow."
"In general, JIRA has no relation to customers or financials. Therefore, marketplace add-ons are needed to make it work for customer-facing systems."
"A lot of users have said that they want a feature that was on the on-prem version of Jira and the vendor can't deliver. They're either unwilling or unable to give feature parity."
"If we can have an easier way to deploy this solution without the help of a consultant and a more reliable way of deploying procedures, it would be quite helpful."
"Jira has different modules that can develop workflow for demand management and project management, but the solution is no out of the box and would require lots of customization."
"The solution needs to be integrated better with Office X5."
"JIRA Service could benefit from improvements to its voice support."
"We found a few issues with importing data and all the manipulation of data, especially when it came to the BI side of things because it utilized a particular template to be able to get certain reports."
"The refresh cycles for our dashboards could be better. I keep complaining about that. The refresh is supposed to be once a day, but I would love it if it was real-time so that if I make a change to the data in iServer, I should see those changes immediately reflected in the dashboards. They use Power BI, and it seems they've scheduled their refresh to be once a day, which is not that good for us."
"We found a few issues with importing data and all the manipulation of data, especially when it came to the BI side of things because it utilized a particular template to be able to get certain reports. The user administrators could not manipulate it to get the right reports."
 

Pricing and Cost Advice

"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."
"For the people like us, the lower the price, the better. But when compared to other competitors, I think it's Jira's price is okay."
"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."
"It costs around $150 to $200 per user."
"I would suggest to always buy licenses through an Atlassian partner, so you can also rely on their expertise."
"Actually in Iran we don't have copyright or intellectual property, so we can use JIRA for free."
"It is a cheaply priced product."
"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."
"The licensing is on a yearly basis. We currently work with a standard fee."
"It was very cost-effective as compared to the other ones we evaluated. We spent about $20,000 per annum for support and license together. There was also an implementation fee at the beginning. I would rate it a nine out of ten in terms of pricing."
report
Use our free recommendation engine to learn which IT Service Management (ITSM) solutions are best for your needs.
894,738 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%
Government
17%
Financial Services Firm
10%
Manufacturing Company
10%
Insurance Company
9%
 

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

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
Information Not Available
Find out what your peers are saying about JIRA Service Management vs. OrbusInfinity and other solutions. Updated: April 2026.
894,738 professionals have used our research since 2012.