HaloITSM vs. Jira Service Management

If you want a value for money full system, which you could use out of the box then this is the one for you. If you want a system that can take care of tasks then this is the one for you. [HaloITSM] is easily scalable with very competitive pricing. New features are added regularly based on best practices and customer requirements.

Incentivized

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

• The Self Service Portal is very easy to configure and the end-users have commented on how easy it is to log and manage their own calls.
• Asset and User Management works very well and it is simple to link them to tickets. Looking up ticket history for particular Users or Assets is also very useful.
• The ability [to] use different ticket types and templates is fantastic. The added ability to merge and clone tickets is also a great benefit.

• 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

• Support for M365 \ Power Platform, Power Bi reporting in particular
• Feel the asset management side of the product is not as good as the ticket management
• Support is excellent but maybe an old school user forum where other admins can share and discuss ideas

• 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

Its simple and intuitiuve - requires minimal training to get people in and working at speed

I gave JIRA a score of 9 since I am happy with the service it offers. I can easily see the SLA since it gives me visibility. I can pull up the reports I need. I can reach out to our clients using the PR ticket so it is hassle-free for me.

I've made overall positive experiences with the Halo support. The only thing to increase would be some follow ups on feature requests. If someone would reach out to me, telling me wheter or not my feature request will be considered in future updates or not.

Incentivized

I have not used the technical support from Atlassian. In terms of online help and resources, they are a bit limited thus making it more of a challenge to troubleshoot issues and learn more functionality. There aren't a lot of resources available on the Atlassian site besides developer documents. It would be nice to have a blog or forum where users can get the help they need.

Incentivized

HaloITSM offered the highest level of functionality, available as standard, at our price level. Halo support during our trial period was second to none and unrestricted. We had a list of deciding factors covering the most important areas of functionality and HaloITSM covered all of these.

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

• It enabled us to allow our Service Desk Staff to work from home during COVID and this has continued ever since.
• We have halved our average resolution time.
• Some of the automation processes, when implemented alongside the MS Power Platform, have saved approximately 30 hours a month. This includes times when customers were unable to access the system until they had been trained. This is now automated via Halo and they get sent to on-demand training, instead of waiting up to 3 weeks for the next scheduled session.

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