-
Suggestion
-
Resolution: Unresolved
-
21
-
Issue Summary
When viewing a list in Jira Work Management, you can apply filters (e.g. labels) to display specific issues.
When doing so, the list will not display issue hierarchy. For example, applying a filter by label will make the parent/Sub-task relation disappear from the list.
See the recording: List filter behaviour.mp4
- In that case, JWKP-8 is a Sub-task of JWKP-6
- When I apply the filter, the Sub-tasks are displayed out of their parents (different from the default view where they appear under the parent issues)
Suggestion
Have the list display the results with the parent/child hierarchy.
- is duplicated by
-
- Closed
[JWMCLOUD-140] Have the list keep displaying parent/child relation aka nesting when applying filter
+1. In instances it makes sense that a custom field would kill the nested view of issues, however if i want to see the projects running for a assignee and it kills the nested view that doesnt make sense to me.
Super frustrating not being able to single out a particular project as well across a timeline, if we're working on a single company in particular and want to track their project progress without seeing every other project being worked on.
+1 Please! This is a preferred view of our team and losing the parent/child relationship increases our time spent sifting through work. It not only becomes unmanageable for our team, but has also started conversations to churn away from this product and move to something else.
I just discovered this view problem today. As soon as even one filter is applied, it breaks the nested view layout and makes a weird view with the issues.
Without filter applied:
With filter applied:
Limited workaround:
We were usually trying to filter on one thing - e.g., a team member trying to see only their issues. So what we found is that when you group the issues in the list view (by Status, Category, Assignee, or Priority), you can drill down into that group and the nested view remains. However, when you try to add on any filters on top of that, it breaks the nested view again. I suppose sorting some of the columns could help get around this so you can see things together?
Tagging the folks who have contributed here so far in hopes that the little workaround we discovered might help you, if even partially! lalmeida@atlassian.com 6d39303f89f4 b9a22543c0f6 6c0d9fb25456
+1 - This is a preferred view for our team. Unfortunate that you are unable to filter material and have child issues nest in the parent since this view displays every issue in the project.
This is crucial as without it the volume of issues in the list view becomes un-manageable. Especially given the fact that the list view is showing all issues within a project and not using the filters associated with the board to reduce the scope of issues.
+1 - this is insanely frustrating and would be amazing if it could be fixed so that it keeps the parent/child relationship in view once a filter is applied...
+1
This is definitely a must-fix. It's super hard to organize the team without this simple feature.