nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

hierarchy ranking in advanced roadmaps

CC_pcyuge

Our hierarchy in Advanced Roadmaps is Theme, Initiative, Epic, Story, Sub-task.

We have a master plan which includes multiple themes(+20). There are 14 scrum boards and a handful of filters in the master plan. The plan is currently ranked by theme and the filter is Theme to Sub-task.

issue: When I change the hierarchy from Initiative to Sub-task, the initiatives don't follow the Theme ranking. Same situation when I change the filter hierarchy from Epic to Sub-task.

For Example,

1. Theme

1.1 Initiative

1.1.1 Epic

2. Theme

2.1 Initiative

2.1.1 Epic

When I change the filter (Initiative - Epic) the ranking does not persist.

2.1 Initiative

1.1 Initiative

Any thoughts?

Accepted answers

Antuan Sammak

Hi @CC

when you are mentioned that your tickets are ranked by theme, i am assuming you are relying on the jql query, am i correct?

if so, please share a snapshot of your query that your plan is reading from.

if not, can you please elaborate a bit further how you are setting up the ranking.

regards,

All comments

Antuan Sammak

Hi @CC

when you are mentioned that your tickets are ranked by theme, i am assuming you are relying on the jql query, am i correct?

if so, please share a snapshot of your query that your plan is reading from.

if not, can you please elaborate a bit further how you are setting up the ranking.

regards,

CC_pcyuge

I'm using the default ranking functionality in Advanced Roadmaps. I change rank by dragging and dropping issues within the plan. The plan is using multiple filters and multiple boards.

Antuan Sammak

Hi @CC

Apologies for not getting back earlier to you on this but i was on holiday.

sorting tickets by Rank means that user has the flexibility of change the order of tickets as you wish, so what you apply on themes is not automatically applicable on initiatives since you have applied different hierarchy, my recommendation is to go to filters and keep hierarchy inclusive all types and on issue types drop down select the ones that you only want to see (excluding themes) then you will have a view showing themes but greyed out and under each one you will have the children tickets.

Would appreciate if you can try the above and let me know if it helps.

Regards,

CC_pcyuge

Thanks @Antuan Sammak that worked!!!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

hierarchy

advanced-roadmaps