Jira Service Management vs. OpenText Service Manager

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

HP Service Manager (HPSM) is well suited for a big company and it does the job that it's intended to do but it's not perfect. It has a fairly large learning curve for searching Knowledge Management (KMs) and it takes time to learn how to be fast at creating/resolving tickets while on calls. I have been using HPSM for about 2 years now and we recently moved from the desk client to the web client and we are seeing a lot more issues than we did with the desk client. They keep coming out with updates for it so eventually most of our issues will hopefully be resolved. Overall the web experience is better as it looks more modern than what we used in the past.

Incentivized

• Manageable workflow to ensure all users follow the same process.
• Can ban boards for easy visual of ticket status.
• Very flexible tool that can adapt to lots of different uses outside of the traditional service desk model.
• Added communication tools help you get out of e-mail jail.

Incentivized

• Capacity management like maintaining CI's and their relations is good.
• Approvals with HPSM is a cake walk and quite logical.
• There is no wait for troubleshooting or help, HPSM tech help is always there.

Incentivized

• Ability to control the number of email notifications received (Note: this is a new feature in the Latest release but I personally haven not extensively looked at it and how well it solves the existing problem).
• No way to reply to multiple tickets at once, say you got 4 tickets in for the same issue, there is no way you can reply to them in one stroke. Other Ticketing systems do have this ability.
• Using a large number of add-ons to customize and add additional features adds up quickly and can become rather expensive.
• Request forms are very basic and there is no native dynamic field ability available.

Incentivized

• 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.

Incentivized

Jira Service Management tool will serve it's purpose to do what it is meant to be. It has it's own limitataions on few features, however it's the industry standard ticketing tool. All covers all the processes that required to resolve the issues. It has various use cases in incident management, Request management etc.

Incentivized

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.

When I evaluated Spiceworks, it was not going to be replacing any ticketing systems. However, I did evaluate it and was not extremely impressed by the short demo I did. JIRA was selected because a branch of our company was already using it, so it made sense to consolidate into one service desk solution, and JIRA was the better option since it was less expensive and geared towards being a ticketing system.

Incentivized

[We selected HP Service Manager because] HPSM is reliable.

Incentivized

• JIRA has been incredibly useful. Our work is more organized and easier to view by the team members as well as upper-level people.
• Our work is correctly assigned and when there are issues, they can be immediately addressed within the tool.
• Users can attach screenshots or files of issues that help clarify the ticket. Developers can attach relevant data as well.

Incentivized

• We take anywhere from between 850-1400 calls a day and overall the whole opening tickets to close process goes pretty smoothly.

Incentivized