InvGate Service Desk vs. Jira Service Management

This is well suited for someone who is looking for a basic help desk system (like we were). This product will get you out the door, but after owning it for several years now we have begun to look for more. The hardest part is that you cant get to raw data to use with other BI tools. If you want major customizations you will be limited

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

• Set-up of system.
• GUI is user-friendly.

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

• The database for back-end is clunky and cryptic, and it is very hard to access data.
• The reporting functions are really lacking.

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

This is one area where they need a lot of help, especially for being selling an ITSM. The service desk is located in Brazil, and they have very few individuals that speak English. Multiple updates over the year have broken the language of the system and tickets have come out in a foreign language. Support is unable to fix issues that occur where downtime occurs. Updates are too fast. Revisions happen 3-4 a week.

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

At the time of comparison, InvGate had a better price and way quicker set-up time to get it up and running

Incentivized

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

• Upfront, it had a very good ROI compared to a homegrown system that was being used.
• Allows users to submit issues to get MFG back up and running.

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