Jira Product Discovery Explained: What It Is and When to Use It

[#1]

Every product team collects more ideas than it can build. They come from sales calls, support tickets, user interviews, and internal brainstorms, and most never receive a proper review. Collecting them is the easy part. The hard part is organizing them, deciding which ones deserve engineering time, and explaining that decision three months later.

In this article, I explain what Jira Product Discovery is, when teams reach for it, and how to configure your first space step by step. You will also find a free product discovery checklist that our team runs before any idea reaches JPD.

Real-life definition of Jira Product Discovery: what it is and what it does

Definition

Jira Product Discovery, often abbreviated as JPD, is an Atlassian tool for capturing ideas, prioritizing them, and building product roadmaps. It runs on Jira Cloud and gives product managers a single place to gather product opportunities, attach evidence, score them against custom criteria, and share the outcome with everyone who needs to see it.

For comparison, if Jira Software contains work your team has already agreed to deliver, JPD contains everything that has not yet earned that status. This includes rough concepts, customer feature requests, competitor findings, and suggestions from sales or support.

Having a centralized place for all this information is valuable for agile teams. The cost of building without evidence can be quite high. Atlassian's State of Product 2026 Report found that 84% of product teams doubt the product they are working on right now will succeed in the market. 

CB Insights approached the same question from the other end. Its Top 9 Reasons Startups Fail report, published in March 2026, named weak product-market fit among the leading causes in 43% of the failures it reviewed. Both figures describe one gap. Teams often commit to building things before they have proof that anyone wants them.

Jira Product Discovery solves this problem by keeping the evidence next to the decision it supports. Research notes, customer quotes, and analytics all live on the idea itself, where the whole team can read them.

Here is what you can do with it:

• Capture ideas from several entry points and keep them in one structured backlog
• Attach customer feedback and research findings to specific ideas as insights
• Score and prioritize ideas with custom fields and tailored formulas
• Compare options in list, board, matrix, and timeline views
• Build a product roadmap and publish it to internal or external stakeholders
• Connect committed ideas to Jira epics and follow delivery progress from JPD

Hands-on tip: before you start working with Jira Product Discovery

There is one thing worth settling before you create your first project. JPD gives you an excellent home for ideas, scores, and roadmaps, but it does not walk you through the research stage that produces them. You will still need to interview users, review data, test rough concepts, and turn observations into evidence. Without a defined and well-structured process for that part, discovery can become inconsistent and chaotic.

"People sometimes think that Jira product discovery will give them an end-to-end solution for managing this process, but it's not quite so. JPD is great for collecting, prioritizing, and managing ideas and other inputs but it does not walk you through the actual product discovery and validation process. For this reason, we use our Product Discovery Checklist template to run this process consistently. Once the research is complete, we move over to Jira Product Discovery and work with the ideas it produced." 

Oleksandra Sokol, Product Lead at TitanApps

You can follow this tip and use our free Product Discovery Checklist template to better organize your work at this stage. 

# Product Discovery – Step-by-Step Checklist

## 1. Define the Problem and Goals

- Describe the problem you want to solve in simple terms

- Identify who is affected and in what situation

- Define what you want to understand by the end of discovery

## 2. Identify Users and Key Assumptions

- Define the primary and secondary user groups

- List assumptions about user needs and behavior

- List assumptions about business value or impact

## 3. Explore Solution Directions

- List possible ways to solve the problem

> Keep solutions conceptual, not detailed

- Note major constraints (technical, legal, timing)

## 4. Run Discovery Activities and Gather Evidence

- Select discovery methods

> User interviews, desk research, data review, prototype feedback, etc.

- Prepare discussion guides, questions, or scenarios

- Run discovery sessions or research

- Analyze the results and adjust your solution based on your findings

- Define the next steps and owners

## 5. Validate your solution

- List the key risks and concerns

- Choose the validation method (prototype test, pilot, experiment)

- Create the simplest version of your product needed for testing

- Prepare realistic tasks users should complete

- Run validation sessions with the users and record results

- Analyze the outcomes and list required changes

To add this checklist to your Jira work item, you can use our solution, Smart Checklist for Jira. It adds feature-rich checklists to any work item in Jira Software and Jira Service Management, so the discovery steps live inside the ticket rather than in a separate document. After installing it, copy the template above and paste it into the Smart Checklist section of your work item. The markdown formatting will be visualized by Smart Checklist as a structured list.

From there, you can assign individual checklist items to teammates and set per-item deadlines and priorities. You can also mark critical steps as mandatory and configure a validator so that the work item cannot move to Done until all are complete. Smart Checklist also allows you to save this and other checklists as templates for future use.

For a fuller version of this process, please see our article A Free Product Discovery and Validation Template.

When do you need to use Jira Product Discovery? Typical scenarios

Jira Product Discovery is a fit for any team that collects feedback and data on an ongoing basis and turns it into a roadmap. In practice, teams reach for it in a handful of recurring situations. 

Here are the most common ones:

• Preparing to launch a new product. The months before a launch produce more ideas than the first release can hold. You need one place to collect them and decide what belongs in version one.
• Collecting feature requests from multiple sources. Requests can come from sales calls, support tickets, customer interviews, and internal suggestions. JPD gathers them into a single backlog rather than leaving them scattered and forgotten.
• Prioritizing a long backlog against shared criteria. Past roughly fifty ideas, ranking by discussion stops working. Custom fields and scoring formulas provide everyone with a consistent metric for comparing product opportunities.
• Planning the roadmap for the next quarter or year. Planning works better with live data than with a static deck. You can sort ideas by score, weigh the top items against capacity, and agree on what to include in the Now, Next, and Later plan sections.
• Aligning several product teams on one process. Larger organizations run into a comparison problem when each team scores ideas its own way. A Jira admin can set up global fields so that every team scores ideas using the same criteria. On the Premium plan, cross-space roadmaps can roll up every team's plan into a single view for leadership.
• Connecting discovery to delivery in Jira. Teams already running engineering work in Jira Software adopt JPD to link the two stages. An approved idea becomes a Jira epic with its context attached.

The list is not limited to product management. Marketing teams can use the same setup for campaign ideas, and program managers can apply it to initiatives that span several departments.

How different roles use Jira Product Discovery

Discovery is rarely a solo activity, and JPD is built around that. Product managers own the space, but the tool's value grows with the number of people who contribute to it. The table below shows how each role typically participates and what they get in return.

Role	How they work in Jira Product Discovery	What it gives them
Product managers and product owners	Own the space, define fields and scoring, run prioritization, and build the product roadmap	A ranking of product opportunities they can defend, and a roadmap ready to share
Engineering managers and tech leads	Comment on ideas, add feasibility notes, and give rough effort estimates before anything is committed	Early sight of what is coming, plus a say before work reaches the backlog
Sales and customer success	Submit feature requests and attach customer quotes from calls as insights	Visibility into what happened to the requests they raised
Support teams	Link recurring tickets to the relevant ideas so repeated pain becomes a countable signal	Proof that frequent complaints are tracked rather than lost
Marketing	Add competitor and market findings to ideas and follow what is moving up the roadmap	Lead time to prepare positioning and launch messaging
UX researchers and designers	Attach interview findings, usability results, and prototype feedback to specific ideas	Research that stays connected to decisions instead
Executives and other stakeholders	View published roadmaps, cast votes on ideas, and comment in shared views	A current picture of direction without asking anyone for a status update

9 Jira Product Discovery Capabilities You Should Know About

Jira Product Discovery is a focused tool with a specific job. It does not cover the entire product lifecycle, and most of what it offers falls into three groups. First come the mechanics of capturing an idea and the evidence behind it. Then there are the tools for comparing ideas and presenting the results to others. Finally, there is the connection to Jira Software, where committed work gets built.

The nine capabilities below cover all three groups. Understanding what each one does will help you decide how much of the tool your team actually needs.

1. A dedicated work item type for ideas

Everything in a discovery space is built around a single unit. An idea is a work item type of its own, so it holds a description, comments, attachments, and any fields you add to it. That structure is what lets you filter, sort, and score ideas later.

You can also merge two ideas when they turn out to describe the same opportunity, archive the ones you decide against, and restore them if the situation changes. Ideas support templates as well, which helps when your team writes up opportunities in a consistent format.

2. External integrations for collecting ideas

Most feature requests reach a product manager outside of Jira. A customer mentions something on a sales call, support closes a ticket with a workaround, or a colleague drops a comment in a Slack channel.

Jira Product Discovery connects directly to several of these sources. You can create an idea from a Slack or Microsoft Teams message, from a Jira Service Management request, or from any web page through the Chrome extension. Teams that collect requests company-wide often add an intake form, so people can easily submit ideas for triage.

3. Supporting evidence stored as insights

An idea on its own is an opinion. Insights are the pieces of data you attach to it: a quote from a user interview, a link to a support ticket, a note from a sales call, or a screenshot of an analytics dashboard.

Each insight retains its source link, so anyone can trace a claim back to its source. Two details make insights particularly useful during prioritization. One insight can be attached to several ideas at once, which matters when the same piece of feedback touches more than one opportunity. And the number of insights per idea is counted automatically, giving you a rough signal of how often a problem comes up.

4. Idea scoring with custom criteria

Product teams rarely agree on priorities in the abstract. Fields give you a way to make the reasoning explicit. Alongside the built-in ones, you can add fields such as Reach, Business value, Effort, or Product area, and choose the type that fits each: a rating, a number, a single-select, and so on.

Formula fields then calculate a score from those inputs. You can build a weighted score that normalizes values across the space, roll up numbers from other fields, or write your own expression for a framework like RICE. The result is a shared scoring model that your team can inspect and debate, rather than arbitrary ranking that lives in one person's head.

5. Four view types for the same idea backlog

Your backlog can be presented in different ways depending on the question you are asking. Jira Product Discovery gives you four ways to look at the same set of ideas, and you can create as many views of each type as you need.

• List view shows ideas as sortable, filterable rows with your fields as columns. It suits backlog reviews and detailed comparison
• Board view groups ideas into columns by any field. It is the usual choice for a Now, Next, and Later roadmap
• Matrix view plots two fields against each other, such as impact versus effort. It works well in prioritization workshops
• Timeline view spreads ideas across weeks, months, or quarters, which helps when you need to show rough dates

Every view stays live. When a field value changes, all views that use it are updated.

6. Roadmap sharing with external stakeholders

Roadmap conversations usually involve people who do not work in Jira day-to-day. For them, you can publish a view as a link that opens outside your Atlassian site, so no account is needed to open it. Please note that you may need a paid plan to have access to this functionality.

Views can also be embedded in a Confluence page, which is useful when the roadmap needs written context. Since each view has its own filters and fields, you can prepare one version for leadership and another for the engineering team without maintaining two separate documents. Export to CSV, Excel, or Google Sheets is available for users who need the raw data.

7. Voting and commenting for contributors

Not everyone who has an opinion on the roadmap needs a paid seat. Contributors are free users with an Atlassian account, and they can comment on ideas, react to them, and vote for the ones they care about.

This is how sales, support, and engineering stay involved without becoming administrators of your space. Their votes also work as an input you can sort by, alongside the insight count and your own scoring formula.

8. Connection between ideas and delivery work

An approved idea has to reach the team that will build it. In Jira Product Discovery, the handoff occurs on the idea's Delivery tab.

There, you can either create a new work item in a Jira Software space or link the idea to existing ones. When you create a new one, you can copy the idea description and fields into it. Engineers then open a task that already explains the purpose of the work. The connection stays active after that. As the linked work items move through their workflow, their progress appears on the idea and in your views.

9. Automation templates for routine updates

A discovery space accumulates small maintenance tasks. You need to archive shipped ideas, create delivery work items, and notify stakeholders when something changes status.

Jira Product Discovery ships with a library of automation templates for these cases. You can turn on a template, adjust its values for your space, and it will run from then on. Space admins manage templates for a single space, while Jira admins can enable global templates across every discovery space on the site. Custom rules (flows) are available too, if none of the ready-made ones match your process.

User roles in Jira Product Discovery: creators, contributors, and stakeholders

Access in JPD is divided into three types, and it is worth understanding before you invite anyone:

• Creators are the people who build and run the space. They create projects / spaces, define fields and views, add and edit ideas, and configure prioritization. Product managers almost always fall into this group.
• Contributors are everyone else who participates. They only need a free Atlassian account, and they can add insights, submit ideas, vote, and comment. What they cannot do is change project / space configuration, fields, or views.
• Stakeholders are people who only open a published view. They have no access to Jira or any other Atlassian Cloud product, all they can see is the read-only view you share with them and nothing else. However, they will still need a free Atlassian account.

This distinction matters directly for your bill. Only creators consume paid seats. Contributors and stakeholders are free and unlimited, and neither group counts toward your license. That is what makes company-wide participation practical. You can invite the entire sales team to submit feature requests without paying for a single extra license. You can also share a roadmap with leadership or customers without adding anyone to Jira. When you plan your rollout, count the people who will genuinely configure and curate the space. Treat everyone else as a contributor, or as a stakeholder if all they need is the roadmap.

6 steps to configure Jira Product Discovery

Setting up a working space takes roughly an hour if you already have a Jira Cloud site. Here is the sequence we recommend.

1. Create your Jira Product Discovery space / project. Sign up for JPD at atlassian.com, or add it to your existing Jira Cloud site. In your Jira instance, go to Spaces -> Create space and select the Product Discovery template. Keep in mind that JPD spaces are team-managed only, so each space is self-contained and its configuration does not affect other spaces.
2. Define the custom fields your team will score against. Open the list view, click the plus sign in the empty column on the right, and select a field or create a new one. Start with five to seven fields, as too many fields at the start can discourage contributors. Common choices are Reach as a numeric field, Business value as a rating, Product area as a single-select, and Customer segment as a multi-select. 
3. Set up your prioritization formula. Add one more field, choose the custom formula type, and select weighted score, roll up, or your own expression. This turns the individual inputs from the previous step into a single ranking number you can sort by.
4. Add ideas and fill them with context. Bring them in through whichever channel fits your team: manually with the Create button, via Slack, Jira Service Management, or the Chrome extension. Larger organizations often add an intake form so anyone in the company can submit an idea without JPD access. Then write a clear problem statement for each idea, fill the custom fields, and attach insights as evidence. Here’s an example of an idea work item in Jira Product Discovery:
5. Build views for each audience you talk to. Prepare a list view sorted by score for internal grooming, a matrix view of Impact vs Effort for workshops, a board view grouped into Now, Next, and Later for engineering, and a timeline view for leadership updates. Filter each view down to the work items that the audience actually needs.
6. Connect committed ideas to delivery work. Open the idea, go to the Delivery tab, and select Create work item to add a new Jira epic or task. Select Link a Jira work item to connect an existing task. Check the option that embeds the idea description and fields, so the engineering team receives the full picture. 

Key differences between Jira Product Discovery vs Jira Software vs Confluence

A fair question at this point is whether you need JPD at all, given that you already pay for Jira and Confluence. Indeed, many teams assemble something close to it using those two tools, and this setup is worth your attention.

The basis for it is a separate Jira project / Jira space acting as the idea backlog. It gets a custom work item type called Idea and custom fields for impact, effort, confidence, and a score that someone works out by hand. Saved JQL filters and board configurations then stand in for JPD's views. A Kanban board with configured Now, Next, and Later columns serves as the roadmap, and sorted filters serve as a substitute for the ranked list.

Confluence carries the context around each idea. Teams write ideas up from a page template, keep a shared idea register in a Confluence database, and run prioritization workshops on whiteboards. Once an idea is approved, its Jira work item is linked to a delivery epic in the relevant project / space.

The setup works, and some teams run it for years. It also takes real configuration effort and leaves specific gaps. The table below compares all three on the jobs JPD was built for, so you can see which of those gaps would affect you.

Task	Jira Product Discovery	Jira Software	Confluence
Capture ideas from many sources	Native intake from Slack, Jira Service Management, and the Chrome extension	Possible with a dedicated Jira project / space and a custom Idea work item type	Possible with page templates and Confluence Databases, filled in by hand
Score and prioritize ideas	Custom fields plus weighted, roll-up, or custom prioritization formulas	Custom fields only. The score has to be calculated outside Jira or through automation	No scoring. A table can hold numbers, but nothing ranks them
Attach customer feedback as evidence	Insights keep the source link and attribution, and one insight can serve several ideas	Comments and links, with no counting and no reuse across work items	Quotes can be pasted onto a page, disconnected from the backlog
Compare ideas visually	List, board, matrix, and timeline views, all live	Boards, lists, and the Timeline view. No matrix view for impact against effort	Whiteboards for workshops, but not tied to live data
Share a roadmap with stakeholders	Views published externally or shared internally, updated in real time	A board with Now, Next, and Later columns, visible to licensed users	A page that somebody has to keep current manually
Involve people without a paid seat	Contributors join free and can vote, comment, and add insights	Every participant needs a Jira seat	Every participant needs a Confluence seat
Hand committed work to engineering	Two-way sync links an idea to one or more Jira epics across different Jira projects / spaces	Delivery already lives here, but there is no discovery layer above it	Manual linking between pages and Jira work items

Using Jira Software with Confluence instead of Jira Product Discovery has its benefits. It adds no new subscription and runs on tools your team already knows. The trade-offs are concrete, though. Without a formula field, every score must be calculated manually or via automation rules that someone must maintain. Without a matrix view, the impact-versus-effort matrix has to be drawn somewhere outside Jira. Customer feedback lives in comments and pasted quotes, so nothing tracks how often the same request recurs. And anyone who wants to open the roadmap needs a licensed seat, which is usually what keeps the wider company out of the process.

The choice comes down to volume and participation. Stay with Jira and Confluence while the idea flow is low and one person handles prioritization. Move to Jira Product Discovery once several teams need to contribute and your ranking has to hold up in front of the leadership.

FAQs about Jira Product Discovery

What are the best alternatives to Jira Product Discovery?

The main alternatives among dedicated product management platforms are Productboard, Aha!, ProdPad, and Airfocus. Each covers roughly the same ground of idea capture, scoring, and roadmap sharing, and each integrates with Jira for delivery handoff. They differ mostly in how prescriptive the workflow is and how much AI they apply to feedback processing. Another significant difference is pricing - JPD remains one of the most cost-efficient options. For a detailed comparison of pricing, prioritization models, and feedback handling, please see the Jira Product Discovery alternatives section of our guide.

Is Jira Product Discovery free? What is Jira Product Discovery pricing?

Yes, there is a free tier for small teams. It covers up to three creators, 2 GB of storage, and unlimited contributors, which is enough for a solo product manager or a small team trying out the tool. Teams with more than three creators require a paid plan. Standard plan starts at around $10 per creator per month, and Premium at around $25, with the per-creator rate dropping at higher tiers. Our guide breaks down what each plan includes and who it suits. For current figures, please see the official Jira Product Discovery pricing page.

Where can you watch a Jira Product Discovery demo?

Atlassian publishes a pre-recorded, on-demand JPD demo that walks through the core workflow end-to-end. Live sessions with a Q&A are also scheduled regularly and can be booked from the Atlassian website.

Does Jira Product Discovery support product roadmaps?

Yes, and roadmaps are one of the main reasons teams adopt it. You can build a roadmap as a board view with Now, Next, and Later columns, or as a timeline view spanning quarters. Both stay live, so the roadmap reflects the current state of your ideas without manual updates. You can publish a view to external stakeholders through a shareable link, or share it internally for comments and votes. The Premium plan adds roadmap views that aggregate several product teams into a single portfolio view.

Can you use Jira Product Discovery without Jira Software?

Yes. JPD works as a standalone product and does not require a Jira Software or Jira Service Management subscription. You can run it on its own Atlassian Cloud site or alongside other Atlassian products on the same site. The trade-off is the two-way sync. Without Jira Software, ideas have nowhere to hand off to, so you lose the link between a prioritized idea and the delivery work behind it. Many teams start with JPD alone and add Jira Software once they reach the next stage.