Jira Service Management (formerly Jira Service Desk, now including features from the former Mindville Insight, acquired by Atlassian in June 2020) is a service desk software that is purpose-built for IT, service, and support teams. The software provides everything IT and support teams need out-of-the-box for service request, incident, problem and change management. Jira Service Management integrates seamlessly with Jira Software so that IT and development teams can work better together. Users…
$0
per month
OpenText Service Manager
Score 9.0 out of 10
N/A
OpenText™ Service Manager (formerly from Micro Focus) is scalable service desk software powered by machine learning, analytics, and automation. It provides an ITSM platform for standardizing service delivery and support across the enterprise.
N/A
Pricing
Jira Service Management
OpenText Service Manager
Editions & Modules
Free
$0
per month
Standard
$20
per agent/per month
Premium
$40
per agent/per month
Enterprise
Contact sales team
No answers on this topic
Offerings
Pricing Offerings
Jira Service Management
OpenText Service Manager
Free Trial
Yes
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Jira Service Management
OpenText Service Manager
Features
Jira Service Management
OpenText Service Manager
Incident and problem management
Comparison of Incident and problem management features of Product A and Product B
Jira Service Management
8.2
Ratings
1% above category average
OpenText Service Manager
9.4
Ratings
15% above category average
Organize and prioritize service tickets
7.50 Ratings
8.60 Ratings
Expert directory
9.00 Ratings
9.60 Ratings
Service restoration
9.50 Ratings
8.70 Ratings
Self-service tools
7.00 Ratings
9.80 Ratings
Subscription-based notifications
10.00 Ratings
9.80 Ratings
ITSM collaboration and documentation
7.00 Ratings
9.80 Ratings
ITSM reports and dashboards
7.50 Ratings
9.80 Ratings
ITSM asset management
Comparison of ITSM asset management features of Product A and Product B
Jira Service Management
10.0
Ratings
20% above category average
OpenText Service Manager
9.7
Ratings
17% above category average
Configuration mangement
10.00 Ratings
9.70 Ratings
Asset management dashboard
10.00 Ratings
9.80 Ratings
Policy and contract enforcement
10.00 Ratings
9.50 Ratings
Change management
Comparison of Change management features of Product A and Product B
Great to manage your issues in a clear and centralised way. If your development teams work with Jira, it will all naturally come together. Great way to manage the issues from end to end. - Very flexible if you have people who understands the set up and is able to configure it for your needs - Maybe not the best if you want something with very easy set up
I would definitely recommend HPSM after working with various other ticketing tools, as it supports and provides the best value and user friendly and quite adaptive to the modern technology mainly the SMS feature, where users were notified for any issues when there are tickets raised. Upgrades and the support provided by the HPSM tech staff is commendable.
Some of the built-in functions and workflows are surprisingly limited given the fact that you can customize a lot with JQL. These limited areas do not allow you to use JQL. For instance, the built-in notifications are lacking. They have one that is great-- "notify on critical ticket creation"-- EXCEPT that it does not allow you to notify a group or anything, only individual users.
The ticket interface is a little odd for agents. Changing the status is not a simple drop down from unassigned to open to in progress to pending, etc. There are a couple of tabs ("investigate", "pending", "workflow") where you can change the status in different ways. Maybe I am just not used to this way of doing it, but I feel like it could be simplified.
It can get complicated deleting/changing some of the out-of-the-box fields and rules, because you never know what will break workflows or other automated/built-in features.
When you search Knowledge Articles, it is not like Google, and you need to learn how to search for what you need.
It takes a very long time to close tickets in HPSM. Here are the steps to close a ticket. 1. Add notes. 2. Add KM 3. Click Resolve 4.Click Save 5.Click Close 6.Click Okay to Message (ticket has recently been modified) 7. Click Close.
It's slow and sometimes crashes/freezes and you lose all the information you may have entered. I usually use notepad++ to gather all my notes and paste them into HPSM.
When searching previous tickets the preview pane does not allow for sorting by date to have the most recent at the very top every time you pull up previous tickets. Sometimes there are pages and pages of previous tickets and you have to click and scroll to get what you need.
I click on search KMs and it takes me to a blank page and I have to click the back button which then brings me to the search KM page.
I have given this rating because, in my opinion, I don't see any downsides of Jira until now. We can customise workflows based on the project needs, including task workflows. Jira is very extensible, which is one of its most important features.
I gave JIRA a 9 rating since for me JIRA works according to its purpose. Since there is a customer portal, our clients can leave a comment or communicate with us using the PR ticket that way it is easier for us to also request any additional information we need for our investigation.
We chose Jira Service Management due to its easy integrations with the rest of the Atlassian tools, as we have also invested in those. For the price, the ability to add or remove agents, and the cost being reflected in that, it was an excellent medium for us. For the foreseeable future, I do not see us moving off this platform.