Jira Service Management vs. UserVoice

I think using a ticketing system is very easy to use and allows multiple teams to create help desks in the same portal. In terms of internal usage, I think this is a great option. However, suppose you're trying to keep internal items and external helpdesks in the same instance. In that case, this is not ideal, as there is no effective way to separate the two instances to protect internal data better.

Incentivized

UserVoice can be an affordable and powerful tool to start engaging customers and employees. It can help manage the entire feedback loop process. But your product management and development teams still need to do their jobs. Remember to have a response SLA in place and ownership for prioritizing and responding to the feedback.

• Integration with many of the most common tools companies are using (Slack, MS Teams, Salesforce, ... etc)
• Natural workflow with Jira (as product development / project management tool) which makes the full fix and follow up of the tickets / issues very easy to follow
• Allow multiple different entry points and work flows for as many different needs your teams / company have

• User interface is very simple. Learning the product and teaching the team how to use the product took hardly any time at all.
• Gives visibility into what others are logging. We are able to append 'votes' to certain ideas, rather than having to create an existing idea from scratch.
• Reporting. Tags allow to easily filter through ideas for roadmap planning.

Incentivized

• Navigating through issues outside of a kan ban board can be confusing and task heavy.
• It's easy to clutter up the tool. It could use some easy clean up capabilities.
• User interface is decent, but could use work to make it more intuitive.

Incentivized

• Doesn't always catch obvious spam/we have to do a fair amount of blacklisting
• Doesn't have multiple language options
• No online/email tech support available. You have to call if you have an issue.

Incentivized

In the current contect the requirments is around having a tool that is focused and can handle large ticket volumes and tracking incident, problem and user requests concerning end users. Jira has built in functionality to address the above practice needs faily easily and has a substantial amount of customizable reports for generating the relevant intelligence.

Incentivized

I just really liked UserVoice.

If you're used to other tools in the Atlassian ecosystem, you'll feel right at home with JSM. It's also a platform that technical folk can easily pick up. However, I wouldn't recommend using JSM as a company's first jumping off point into Atlassian. There are a lot of other 'newer' tools that provide sleeker ITSM systems at a similar cost.

Incentivized

The day-to-day usability is good. More technical settings require a bit more effort.

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.

Always very responsible and helpful when an issue happened. They eat their own cooking when it comes to using their products.

Have clear goals and owners established before you start using any tool like this. Very important to get accounts and rights setup so that there's no lag time in customer response once things go live. Make sure IT is involved if you plan to use the Single-Sign On (SSO) or any of the access control tools.

Zendesk is a similar ticketing system that our organization used before JIRA Service Desk. The main drawback of Zendesk was that it can only be used as a cloud service. This means that our company data would be living on the internet at the hands of their security team. Another drawback of this is the price is significantly more expensive rather than hosting it yourself. Zendesk does have some additional features such as commenting on multiple tickets at once that JSD does lack. However, switching to JSD was significantly more cost effective because we have the ability and the infrastructure to host our own ticketing system, something that Zendesk could not provide. Ultimatley switching to JSD saved us money and allows the ability for integration with all of the other Atlassian Suite products that we use on a day to day basis.

Incentivized

I like the ease of integration into web and mobile apps for UserVoice. It's also a comprehensive bug reporting, user feedback, and knowledge base tool.

Incentivized

• It is definitely cheaper than Salesforce
• It allows the IT service desk to be more organized and respond more quickly to tickets, which can save time for both agent and requester.
• Some things are "not quite there" developmentally, so this means that internal IT will need to spend more time developing and testing the product.

Incentivized

• Transparency: Now we can handle better communication of requests with customers and internal stakeholders.
• We can track better how many ideas are accepted and released vs rejected ones.

Incentivized