Jira Service Management vs. KronoDesk

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 advise my customers to use it for all issue tracking, in business development as well as in business operations. An interface to operational systems is therefor very helpful and enlarges the value of the KronoDesk knowledge base, provided that this information is "open" to all users of all departments.

• 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

• As a system architect I have a clear overview of open issues through clear issue description and assignment to developers.
• The overview and tracking are most important to me.

• 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

• The possibility to create a system/subsystem/component/interface tree of the system landscape, to be used to more detailed issue associations and subsequent detailed planning and monitoring of issues.
• A quick issue entry with the most important information would be helpful.
• A "live" report that can contains my current "hot" issues would be helpful.

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

Several freeware/shareware tools like Bugzilla are missing integration with other systems. HP, IBM and CA like systems are too cumbersome and complicated for "normal" users, for me too much "hassle" to monitor issues and related information and links to other issues.

• 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

• The ROI is reached faster and exponentially higher, depending on the number of users and cooperating business units.