Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,556,856
Community Members
 
Community Events
184
Community Groups

How to get Epics to appear nested under Initiatives in JIRA Advanced Roadmaps

We have figured out how to add 'Initiative' as an issue type, correctly configured the hierarchy, and assigned a Parent Link field to allow Epics to be linked to Initiatives.

 

However, when viewing the Initiative in Advanced Roadmaps, we do not see Epics nested / expandable the same way we are used to seeing a Story nested under an Epic.  Anyone else run into this issue?  

1 answer

0 votes
Roi Fine
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 01, 2020 • edited Sep 02, 2020

Hey @aiden ,

 

Did you make sure the epics linked to your initiative are included in the plan's issue sources? Only issues within the defined issue sources of the plan will be visible in the plan.

You can check out video #2 in this post I made for more details.

I hope this helps,

Roi

Hey Roi, unfortunately the link you added does not seem to be active. Do you mind resharing?

Roi Fine
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 02, 2020

Hey, so turns out it was definitely due to not including the sources.

- While all the correct projects were included, some of the issues/epics were from specific (old) releases that I originally did not include to try and keep things a bit cleaner.  

 

Appreciate the help! 

Like Roi Fine likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events