How to Prioritize Ideas in Jira Product Discovery
Most teams have more ideas than capacity. The ideas live in Slack threads, sales call notes, spreadsheets, and the PM's head, and prioritization happens in whichever meeting has the loudest voice. Jira Product Discovery gives ideas a structured home inside the Atlassian ecosystem, with fields for scoring, insights for evidence, and views for different audiences.
This guide covers setting up a discovery project, defining the fields you prioritize on, attaching customer evidence, building views for triage and roadmap conversations, and linking validated ideas to delivery work in Jira. It focuses on a workflow a PM can maintain weekly, not a one-time spreadsheet exercise.
Before you set this up, check what customers are actually asking for.
Paste call notes, support tickets or feedback. Vantage pulls out the signals and themes in about 30 seconds.
Step-by-step guide
Create a discovery project and define idea scope
Create a Jira Product Discovery project for a product area. Decide what counts as an idea: a customer problem, an opportunity, or a proposed solution. Many teams find it useful to phrase ideas as problems or opportunities and capture solutions in the description, which keeps prioritization focused on value rather than features.
- Create one discovery project per product area or team
- Agree on how ideas should be phrased
- Write a short guide in the project description for contributors
Set up prioritization fields
Jira Product Discovery lets you add custom fields to ideas, including ratings, numbers, select fields, and formula fields that compute a score from other fields. Choose a small set of inputs, such as impact, effort, and confidence, plus a goal field linking each idea to a company objective. A formula field can combine them into a single score. Keep the model simple enough that everyone understands how a score is produced.
- Add fields for impact, effort, and confidence
- Add a goal or objective field to link ideas to strategy
- Create a formula field that combines inputs into a score
- Document what each rating level means
Capture insights as evidence
Insights attach evidence to an idea: a snippet from a customer call, a support ticket, a Slack message, or a link. Atlassian provides ways to add insights from Slack and the browser so the evidence travels with the idea. The number and quality of insights becomes a useful input in prioritization; an idea backed by ten customer conversations deserves more attention than one backed by a hunch.
Build views for different conversations
Views let you look at the same ideas in different ways. A list view sorted by score is good for triage. A board view grouped by status supports discovery stand-ups. A matrix view plotting impact against effort helps in prioritization sessions. A timeline view groups ideas by quarter for roadmap discussions. Save each view with a clear name and filter.
- Create a triage list view sorted by score
- Create a matrix view of impact versus effort
- Create a roadmap view grouped by Now, Next, Later or by quarter
- Filter views by goal or team as needed
Run a weekly triage
Set a recurring 30-minute triage. Review new ideas, merge duplicates, fill in missing scores, and move ideas through your discovery statuses. Focus on the top of the list and new arrivals; you do not need to re-score everything every week.
Connect ideas to delivery work
When an idea is ready to build, create or link delivery work in a Jira software project, typically an epic. Jira Product Discovery can show delivery progress from linked work on the idea, so stakeholders can see where a prioritized idea stands without leaving the discovery view.
- Move the idea to a 'Ready for delivery' status
- Create or link an epic in the delivery project
- Use the idea's delivery progress to report status
Share roadmap views with stakeholders
Stakeholders can be given access to view or contribute to discovery projects depending on your Atlassian setup and roles. Share the roadmap view rather than the triage view, and keep the language outcome-focused so it does not read as a list of promised features.
Common mistakes
Over-engineered scoring
A formula with eight weighted inputs looks rigorous but nobody trusts it. Three inputs that the team understands beat a complex model.
Ideas without evidence
Scores based purely on opinion lead to the same debates as before. Attach insights before an idea can be scored highly.
Treating the roadmap view as a commitment
If stakeholders read every idea in 'Later' as a promise, the view causes more problems than it solves. Label views clearly and explain the difference between discovery and delivery.
Tips
Use a 'Problem' prefix in idea titles to keep the focus on customer needs.
Revisit confidence scores after discovery work; confidence should change as you learn.
Archive ideas that have not gained insights in two quarters to keep the list manageable.
Link each idea to one primary goal so you can see how the backlog supports strategy.
How Vantage helps
Jira Product Discovery decides what to build; Vantage helps you define it. Once an idea is prioritized, PMs bring the customer evidence into Vantage as context, generate a PRD, and produce dependency-aware tickets ready for the delivery tracker, so the reasoning behind the idea is not lost at handoff.