Overview
Jira Product Discovery consulting for product teams and the people who ask them for things
Jira Product Discovery (JPD) is Atlassian's tool for deciding what to build. Product managers capture ideas, attach insights (the customer feedback, data and research that support each idea), score them with fields and formulas, and compare them in list, board, matrix and timeline views. When an idea is approved, it links to delivery work in Jira, so its progress shows in discovery without anyone copying status across. JPD is available on Atlassian Cloud only.
It suits product teams whose ideas live in spreadsheets, slide decks, Slack threads and the inboxes of sales and support, and organisations where stakeholders keep asking what's on the roadmap and why their request isn't. It also suits service and internal platform teams that prioritise requests from the rest of the business, not only software product teams.
Great Minds is an Atlassian Silver Solution Partner with Atlassian's Cloud Migration Delivery and Service Management Sales accreditations. We set up JPD around your product operating model: which ideas get captured, how they're scored, who decides, and how roadmaps are shared. Because we're a systems integrator, we also connect the feedback sources, such as your CRM, service desk and support tools, so insights arrive with the evidence attached. For how a product manager's role fits into this, see our article on the role of a product manager.
Capabilities
What we set up in Jira Product Discovery
A JPD set-up is mostly decisions about fields, scoring and roles. We make those decisions with your product leaders, then configure them, so the tool reflects how you actually prioritise.
How we deliver
A Jira Product Discovery rollout, from operating model to habit
JPD works when it becomes the place product decisions are made, so we design the routine around it as carefully as the configuration.
Workshops with product leaders on what counts as an idea, which evidence matters, how ideas are scored, who decides, and how often the roadmap is reviewed and shared.
Fields, formulas, views, templates and roles, with existing ideas imported from spreadsheets or other tools and cleaned up on the way in.
Feedback sources connected so insights arrive with evidence, and Jira spaces linked so approved ideas become delivery work with progress flowing back.
We run the first prioritisation and roadmap reviews with your team, adjust fields and views from what they learn, then hand over with documentation and training.
Australian considerations
What Australian product teams should check
Data residency. Jira Product Discovery is included in Atlassian's data residency for Australia (Sydney) on Standard, Premium and Enterprise plans, alongside Jira, Confluence and Jira Service Management. Set the location before you import ideas and insights, because moving an existing site's data later involves downtime.
Customer feedback is personal information. Insights often contain customer names, emails and quotes copied from support tickets or sales calls. Under the Privacy Act, collect only what the decision needs: we design insight templates that link to the source record instead of copying personal details across, and restrict who can see raw feedback.
Licensing in AUD. Creators, the people who manage ideas, fields and views, are paid licences. Contributors, who can comment, vote and add insights, only need a free Atlassian account, and stakeholders can view published views without counting towards the licence. Roadmaps that bring views together are a Premium feature. Atlassian invoices Cloud in US dollars, and buying through Great Minds gets you Australian-dollar invoices; see Atlassian licensing in Australia.
FAQ
Jira Product Discovery questions
Who needs a paid Jira Product Discovery licence?
Only creators: the product managers and product operations people who create and manage ideas, fields and views. Contributors, such as engineers, designers, sales and support, use a free Atlassian account and can comment, vote, add insights and, if you allow it, create ideas. Stakeholders view published views and don't count towards the licence.
How is Jira Product Discovery different from a Jira backlog?
A Jira backlog holds work the team has agreed to do. JPD holds ideas that haven't been decided yet, with the evidence and scores to decide them. Keeping the two apart means the backlog stays short and actionable, and ideas that are turned down are still recorded with the reason.
Can we score ideas with our own prioritisation model?
Yes. JPD has standard fields such as impact and effort, and custom formula fields let you build RICE or your own weighted model. We help you choose a model simple enough that people trust the score.
Can sales and support teams submit ideas?
Yes. Anyone with Jira or Jira Service Management access is a contributor by default, and others can be added. We set up a simple submission route and templates so ideas arrive with the customer, the problem and the evidence, not just a feature name.
Is there a Data Center version of Jira Product Discovery?
No. Jira Product Discovery is available on Atlassian Cloud only. If your Jira is on Data Center, our Cloud migration page covers the move.
How do we share the roadmap without giving everyone access?
Publish a view. Stakeholders with a free Atlassian account can see a read-only published view, so leadership and selected customers see the roadmap without editing rights. On Premium, roadmaps can combine several teams' views.
Atlassian products
Jira Product Discovery work usually connects to our other Atlassian services
Discovery decides what to build; the services below cover building it, moving to Cloud and running the platform afterwards.
Atlassian consultingAdvice on site structure, governance and plan choices across Jira, Confluence and JPD.
Atlassian implementationAtlassian Cloud set up with identity, data residency and Jira spaces ready for delivery.
Atlassian cloud migrationMove Jira from Data Center to Cloud, where Jira Product Discovery is available.
Atlassian managed services & supportOngoing administration of Jira and JPD fields, views and permissions after go-live.People
The people behind your discovery set-up
Our Atlassian consultants set up Jira Product Discovery from Sydney, working with your product leaders on the operating model before configuring anything.
The same team connects the feedback sources and the Jira spaces that deliver approved ideas, so discovery and delivery are designed together.
Case studies
Atlassian work for product teams
For a premium kitchen appliance manufacturer, we moved the new product launch process from several disconnected tools onto Jira and Confluence. More than 50 teams and 400 tasks now run on one platform.
Insights
Latest thinking
Strategy doesn’t fail from a lack of ideas. It fails from a lack of clarity on which ideas matter.
Jira Service Management vs ServiceNow: which fits you?Where each platform is strongest, AI and its metering, data residency and IRAP, implementation time and cost profile.
Automation in Jira Service Management: rules, AI agents and integrationsWhat to automate first, building rules well, where AI agents fit, alerting, and automating across identity, HR and CRM.
Getting started with Jira Service Management: a step-by-step guideSet up Jira Service Management in 2026: choosing a plan, request types, queues, SLAs, knowledge, automation, AI and alerting.