Jira Service Management vs. Userlane

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

Well suited:

• Web-based software with many users, complex processes (or both) --> Easy to fix a lot of common support / training issues very fast
• Software rollouts with high costs associated to ensure user acceptance is great --> Great feedback from users
• Multiple applications where processes are adjusted regularly --> Fast to roll out across many apps and easy to maintain

Not so well suited:

• Desktop apps -- > Doesn't really work for desktop
• Mobile apps --> Limited support, only works for web-based mobile apps
• Small user base (less than 50 users) --> Not required when there are only a few users

• 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

• Unbiased people and company.
• Professional team.
• Solution oriented team.

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

• Need to Improve User level analytics
• Need to Improve UX/UI
• Need to improve reporting
• More option to export the analytics report ,Currently you can export in PDF.

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

• Easy to use content editor, no specific knowledge needed
• Super fast to create interactive guides, went live within days
• Clean and actionable analytics, not too bloated

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

I haven't used any other to much extent.

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

• Higher conversion rate.
• Less support needed.
• Proactive communication solves the most user questions.

Incentivized