Jira Product Discovery (JPD) is designed to help teams make better product decisions before work reaches delivery. It sits between strategy and execution, giving product teams a structured way to capture ideas, assess impact, and decide what to build next.
Many teams adopt JPD expecting it to behave like a traditional roadmap tool. Others expect it to replace backlog grooming in Jira. In practice, JPD works best when it’s treated as a discovery workspace, not a delivery tracker or a static roadmap.
This guide walks through how teams are successfully getting started with Jira Product Discovery in 2026, what to set up first, and how to avoid common early mistakes.
Jira Product Discovery is built to support product discovery, not delivery execution.
It helps teams:
Capture product ideas and opportunities
Evaluate impact versus effort
Compare options and tradeoffs
Decide what’s ready to move into delivery
It is not meant to:
Replace Jira boards
Track sprint progress
Act as a detailed delivery roadmap
Understanding this boundary early prevents a lot of confusion late.
Before teams can start organizing ideas and building discovery workflows, Jira Product Discovery needs to be available in the environment. For teams already using Atlassian Cloud, there are a few straightforward ways to enable it, depending on how products are managed internally.
Organizations that manage Atlassian products centrally can enable Jira Product Discovery through the Atlassian Admin Portal.
From the admin view:
This approach is best for organizations that want tighter control over access, licensing, and rollout. It allows administrators to decide which teams can use JPD and how broadly it should be introduced.
Teams can also enable Jira Product Discovery directly from Jira when creating a new project.
During project creation:
This option is commonly used by product teams that already have Jira access and want to start using JPD quickly. It’s a practical path for early experimentation or pilot teams before a wider rollout is planned.
For teams evaluating Jira Product Discovery for the first time, Atlassian offers a free trial.
The trial allows teams to:
This is a low‑risk way to understand the product before committing to broader adoption. Many teams use the trial period to refine how they want to structure discovery work and decide how JPD should be rolled out longer term.
Once Jira Product Discovery is enabled using one of these approaches, teams can move on to creating their first discovery project and setting up the foundations for capturing and prioritizing ideas.
Once teams understand what Jira Product Discovery is meant to do, the next step is getting it set up in a way that supports real discovery work. The goal is not to configure everything at once, but to create a solid foundation that teams can build on over time.
Below is a practical, step‑by‑step approach teams use to get value from Jira Product Discovery quickly, without over‑engineering the setup.
Start by creating a dedicated Jira Product Discovery project.
From the top navigation, open the Projects menu and select Create project. Jira will show a range of templates across different product categories. Look for the Product discovery template, which may appear under Product management or Software development depending on your configuration.
This template gives you the basic structure needed for managing ideas, fields, and views without forcing a rigid workflow. Avoid modifying the project heavily at this stage. The default setup is designed to be flexible and is a good starting point.
Before adding ideas, it’s important to decide who can do what inside the project.
Jira Product Discovery typically distinguishes between:
To manage access:
Getting this right early prevents confusion later and keeps discovery focused. Too many creators can lead to inconsistent setups, while too few can slow momentum.
With the project in place, you can begin adding ideas. Ideas are the core unit of Jira Product Discovery. They can represent customer problems, opportunities, feature concepts or potential solutions.
To add an idea, click the Create button and give it a clear title. Once created, open the idea to add context. This is where teams explain the problem being solved, the opportunity it represents, or why it’s worth exploring.
At this stage, focus on capturing ideas clearly rather than judging them too early.
Fields are what allow teams to compare and prioritize ideas meaningfully.
Open the Fields panel and use the add button to introduce fields that reflect how your team evaluates ideas. Common examples include:
Jira Product Discovery includes several built‑in field types, and teams can also create custom ones. Start with a small set of fields and refine them based on real usage. Too many fields too early can slow adoption.
Fields should reflect how decisions are actually made, not how you think they should be made.
Ideas become more useful when they’re supported by evidence.
Insights can include customer quotes, support tickets, usage data, research notes or slack conversations.
There are two practical ways teams add insights:
Encouraging teams to add insights regularly helps shift discovery from opinion‑driven discussions to evidence‑based decisions.
In Jira Product Discovery, prioritization is not meant to happen in one long, manually ranked list. Instead, teams use views to evaluate ideas based on the specific decision they are trying to make. This keeps discovery flexible and avoids forcing every stakeholder into the same prioritization logic.
Views allow teams to shift perspective depending on context. One view might be used during weekly product reviews, another during roadmap discussions, and another when deciding what is ready to move into delivery. This approach reflects how product decisions are actually made, rather than locking teams into a static ranking that quickly becomes outdated.
When creating a new view from the left‑hand navigation, teams typically choose between a list view or a matrix view. List views are useful for sorting and filtering ideas using fields or formulas, while matrix views help compare ideas visually across two dimensions such as impact and effort.Together, these views make it easier to spot patterns, trade‑offs, and opportunities without over‑engineering the process.
Views support focused decision‑making by helping teams answer a small set of important questions:
Different stakeholders often rely on different views, and that is expected. Product managers, leadership, and delivery teams each look for different signals. The goal is not to agree on a single ranking, but to agree on how decisions are made and which views support those decisions best.
Once ideas are prioritized, teams often create lightweight roadmaps to gather feedback.
Board views allow teams to group ideas into simple buckets like Now, Next, and Later. Timeline views can be used to show rough delivery expectations by month or quarter without committing to exact dates.
Roadmaps in Jira Product Discovery are meant to support conversation, not lock teams into delivery commitments. Sharing views with stakeholders through links, comments, and reactions keeps feedback centralized and visible.
The final step is linking discovery to execution.
When an idea is ready for delivery:
This connection keeps discovery context attached to delivery work. Teams can track progress at a high level from within Jira Product Discovery without duplicating information.
Many teams also create a dedicated delivery view inside Jira Product Discovery to monitor overall progress without diving into sprint‑level detail.
Jira Product Discovery works best when teams treat it as a space for learning and alignment, not as a rigid process to control outcomes. The goal is not to capture every idea perfectly or predict delivery dates with precision. It’s to create shared understanding around what matters, why it matters, and what’s worth investing in next.
Teams that see the most value start simple. They define a small set of fields, create views that support real conversations, and establish clear conventions for how ideas move forward. Over time, they refine their setup based on how the tool is actually used, not how they assumed it would be used.
Product discovery is rarely linear, and Jira Product Discovery is intentionally flexible to reflect that reality. When teams focus on clarity rather than completeness, and on learning rather than perfection, JPD becomes a reliable part of how product decisions are made.
As an Atlassian Platinum Solution Partner, Atlas Bench works with product teams to help them get real value from Jira Product Discovery, not just set it up.
We support teams by: