-
Suggestion
-
Resolution: Unresolved
-
None
-
3
-
Today when you filter the list view that contains a hierarchy of issues the list of issues appears as flat. Instead please maintain the hierarchy, understanding that some of the work would be filtered out of the view based on the filter selected.
Example:
We can see issues that also have their parents in the resulting list of issues after filtering, they show a small parent indication above their issue keys, but the drill-down is lost.
[JWMCLOUD-698] Enable Nested Hierarchy to persist when filtering list & timeline in JWM.
Is there an ETA on this?
There is Issue 111 which is also about the hierarchy problems. That issue has nearly a thousand watchers. You decided to close that issue after a non-complete release (the bugs still exist), and then you opened this one to "gather interest". I think the interest is pretty clear, all those people who wanted hierarchy to exist probably wanted it to still exist after applying filters.
Can we get an update on whether this feature is being worked on? the usage of the timeline view is very limited for a complex project with multiple dependencies. Enabling this would greatly improve our experience with the tool
This issue is so bad. Either I can use the Timeline and its showing ALL TASKS that have ever existed and if I use a Filter it will not display any parent hierarchy and when I try to hide all done items it also hides subtasks that are done, but are important to see for the task management. This makes the Timeline view absolutely not usable for us...
It feels like this ticket isn't really on the radar with the product teams at Jira due to the low number of votes, but in my opinion it's clearly part of this ticket, which has almost 1000 votes: https://jira.atlassian.com/browse/JWMCLOUD-111
I think most users would not consider JWMCLOUD-111 to be complete while this feature is lacking. Will we receive an update on this any time soon?
I agree with Amy. This is very very important for us. How do we get this on the radar??
This is key to retain visibility of epics used to group workstreams in a project. The lack of nested hierarchy makes it extremely difficult to show relevant tasks for an individual and give them an understanding of the big picture / roll up - the tasks lose context when displayed on the screen, and we need this at a surface level.
93038f7213d7 and bb3b5f443b59 can you please help us get this looked at