Showing results forย 
Search instead forย 
Did you mean:ย 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Roadmaps levels in JPD : managing different details levels

Hello all!

I was wondering if there currently is a way to manage different levels of details for roadmaps in Jira Product Discovery.

My need would be to have a detailed roadmap for PMs and a very high-level one for Directors/top management: I'm planning on adding a custom checkbox to select what we want to display to top managers and create a filtered view based on this field for them, but I consider it to be a workaround.


2 answers

1 accepted

Suggest an answer

Log in or Sign up to answer
4 votes
Answer accepted
Tanguy Crusson
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jan 26, 2023

Hi @Quentin C_ the app is all about using custom fields and views to be able to navigate ideas, prioritize collaboratively and communicate roadmaps. With control over what people see. So i'd say that the way you're planning to do it is pretty much what it was designed for. 

It can be based on a checkbox or different fields. 

The way we do it in the Jira Product Discovery team is based on 3 fields: 

  • Type:
    • reliability: initiatives to make sure the app can scale
    • improvements: improvements to the existing product experience and features
    • boulders: new features
  • Phase:
    • wonder (problem/opportunity exploration and validation),
    • explore (solution exploration and validation),
    • make (commitments),
    • impact (further iterations to hit a goal)
  • Roadmap: 
    • Now: current commitments
    • Next: next commitments - usually there's already problem validation there but we're still exploring solutions
    • Later: everything else that's high on our radar

The roadmap we communicate to the company is based on ideas that have values for these fields. What it looks like (sorry, not ready to make the full roadmap public yet ๐Ÿ˜…):

Screenshot 2023-01-26 at 12.29.51.png

We have customers that create different roadmaps depending on the target audience, so they have other fields to represent that. 

If I wanted to be sure only some ideas get shown to stakeholders, I'd use a checkbox as well. 

Hi @Tanguy Crusson 

thank you for sharing this, I love the phases that you're using! I'd also be very interested in seeing the other views like team allocation, boulders & improvements, bets or shipped items - is that something you can share? 

I've added a label for this in JPD and created different views based on that label. Only difficulty I encountered is that I'm not able to select a group of idea tickets as 'delivery'. 

AUG Leaders

Atlassian Community Events