Roadmap loses Hierarchy when using View Settings and Group by Component option

[PJB]

Roadmap loses Hierarchy when using View Settings and Group by Component option.

The roadmap has proper hierarchy from deliverable to Sub-task in the roadmap (Plan) we created.  We can drill into Epic -- Story -- sub tasks if desired.

Issue:  If we add a View and Group By the "Component" field  to the Plan/Roadmap, the Hierarchy goes away and we only see the deliverable level.  If we remove this "Group by"  Component field, The Hierarchy drill down re-appears. 

We have noticed if we group by the Team name field the Hierarchy remains. 

Any suggestions? 

Thank you.

[Trudy Claspill]

Hello @Phil Burgard 

Welcome to the Atlassian community!

Are Team names assigned to the issues at all levels of the hierarchy?

Are Components assigned to the issues at all levels in the hierarchy?

[PJB]

Thank you for the fast response. I’ll have to check To see if components values are present on all work items.

I’m not sure the component field is available on story, task, spike, bug and subtask in our environment.

Do you think it’s needed out the lowest level of the hierarchy in this case subtask?

[Trudy Claspill]

I work with Jira Cloud rather than Jira Server/Data Center, so I cannot confirm if the Component field is actually required at all levels if you want to Group By Components. It was just a theory.

[PJB]

Thank you.