Jira Product Discovery vs. Jira Service Management

It's a great tool for early stage ideation and prioritization in order to get alignment across product, design, and engineering. It works really well when teams are trying to consolidate scattered ideas into one validated pipeline. The scoring model and ability to link ideas directly to our regular Jira makes it easy to prepare for roadmap views

Incentivized

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

• Timeline view of ideas and the way you can group these into different views is fantastic.
• The ability to have connections to the main idea as sub ideas before reaching our delivery teams.
• Admin and feature controlls are great and getting even better.
• Recycling fields and goals from the other Atlassian products makes things easier to see and understand.

Incentivized

• 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

• Advanced Reporting and Analysis: Reporting options are somewhat limited. It would be more helpful if it’s more customisable dashboards
• better Support for cross project visibility: it is challenging to see dependencies overlaps across different projects. It could’ve been improved
• More flexible roadmap customisations: Here customisation options are limited, formatting options could be improved

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

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

Jira Product Discovery is good because it offers a lot in the way of centralising processes for bug management and its intake. However, it is not going to score higher as it has limited reporting and integration features. It also isnt setup to give updates via email to case loggers which would be really good

Incentivized

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

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.

productboard is my favorite, but that one is more Product oriented where Atlassian Jira Product Discovery seems more Dev focused so it is nice those tools compare. Azure is really nice in the UX and the way it presents the sprints and the stories in an easy manner. Atlassian Jira Product Discovery is great when creating the stories within itself and also works with productboard better than azure does currently.

Incentivized

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

• Shared understanding of goals has increased
• Management of large number of work items is good
• Sometimes if we dont manage it well it can get complex and people get lost.

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