HaloPSA vs. Jira Service Management

Having been in IT for 10+ years and used so many different PSA platforms, I must say working with HaloPSA has been simply amazing. Straight out of the box, it's fast. It's feature-rich. It's easy to set up the basics, and the onboarding team was amazing. The onboarding team actually spends time with you, human on human, walking you through the setup and getting it working how you want. No one else does that included. Yeah, sure, you can pay CW and the other huge amounts of money, and they sort of help you, but HaloPSA helps you from the start; it seems they realise if they help set it up correctly in the first place, it reduces support calls. We can run our business from day one - very customer-centric. We have been using HaloPSA for a year now, and there is still plenty to learn and develop on the platform, but every week we are learning new things that we can do. The support team is great; they are humans who understand the issues we face, so they get things working fast. We have suggested some missing features to the dev team, and so far, they have implemented all of them - WOW. Don't get me wrong, as with all platforms, HaloPSA is not perfect. It's young, but it's maturing fast, very fast, and they are getting integrations built with the major players in the IT industry, which is fantastic. Yes, a few times, the link to Xero broke, which was annoying, but unlike the platforms we used in the past, the support team spoke to us and told us what the problem was and got it fixed, so you can't ask for more than that. Their growth has been fantastic to see, but again this has meant a bit of change around with account managers, support personnel, etc., but everyone they bring on is just as good as the last. All in all, migrating to HaloPSA was the best software/platform decision I have made in our business since I began the business. I would recommend HaloPSA to any IT business. Well done, Team HALO. Keep up the awesome work.

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

• Workflows
• Stock Control
• Quoting

• 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

• Stock control
• There are 3-4 different ways to do that same thing
• Documentation

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

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.

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.

We have used and tried several other PSA vendors and HaloPSA was our favorite by far. Many others were either much too overly complicated, clunky, slow to respond to issues, incomplete, or they simply failed to deliver on promises made, especially in terms of integrations.

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

• Improve our technicians efficiency
• Helped improve asset recording
• Knowledge base

• 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