-
Suggestion
-
Resolution: Fixed
-
None
-
1
-
7
-
Currently, if we group Initiative issues by component, for example, and the filter is set to show the full hierarchy, we'll have one section for the Initiatives that have the component on them and another section for all other issues that don't have the component but are still part of the full hierarchy(i.e., Epic, task, story, subtask). This makes the view show that Initiative with child issues twice, one for the component group and another for the full hierarchy.
It is requested that:
- Group the Initiatives by one of their fields (e.g. Component)
- Retain the drill-down capability into the underlying epics/stories/tasks/subtasks, even though those underlying items don't share the field we are grouping by
- Essentially, only have the grouping applied to the Initiative level
- This could even be optional, on the Group By panel. You could have a checkbox "Group only by Initiative field" or similar to selectively control the behavior.
- duplicates
-
JRACLOUD-87660 Jira Plans Group By filters children items
- Closed