Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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!


Different Levels of Hierarchy in Advanced Roadmaps

We are trying to create a high level schedule using Advanced Roadmaps but running into trouble being able to use advance roadmaps to visually look at the plan across the various levels.  In a typical WBS, we might have different levels before we get to the stories and we want to roll them up so we can see all the level 1, 2, 3s, and JIRA but also be able to track stories against them.  

An example is below:


Level 1 – Planning

Level 2 – VOC Alignment, MVP Definition, and Charter Review

Level 3 – These would be the stories that roll up to the Level 2.


Another section though is

Level 1 – Development

Level 2 – Prototype Build 1

Level 3 – Prototype Build Insertion

Level 4 – Design / Documentation

Level 5 – These would be the stories that roll up to the level 4.


Is there a way to do this where we can keep consistent Level 1's vs in the above scenario having to make Planning a Level 3 so that matches in the hierarchy.  

2 answers

0 votes
Roi Fine
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Aug 25, 2020

Hi @JHartma1 ,


That's a good challenge that can be solved in different ways. My tip is to start with a structure that is relatively simple. It's easier to add than to remove structure. When needs come up, you can consider adding more structure.

From a quick glance. Your five levels: development, design, etc.. could be structured as status workflows rather than issue hierarchy. Read here to get up to speed with workflows  

Good luck!


0 votes
Irina Mosina
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Aug 25, 2020


I wonder if representing your process of work breakdown as workflow statuses rather than vertical hierarchy would make more sense. 

You vertical hierarchy can be then : 

"Big Thing" (wether you choose to call Initiative or Project) - Epic - Story/Task

For, example, your "Big Thing" will go through a number of iterations, starting with refinement:  Planning - VOC/MVP. 

Epic/Stories created for Initiatives in these stages will reflect the work that needs to be done at that point. 

Later, once you know more about the feasibility of your project, you move your whole Initiative into Development, then Prototype etc. 

Now your Epics and then Stories are specific and estimated with more certainty. 

With this approach you can actually measure Cycle Time for your Initiatives using built in reports as well as effort that it takes to complete MVPs or Prototypes. 


Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events