Okay header kinda explains it.
When you first enter the list view, you're given all of your issues presented in a hierarchical way (epic -> subtask) as shown on screenshot #1.
But if you decision to filter by assignee or anything really, the hierarchy breaks.
I don't know about you but the expand/reduce indentation is pretty useful visually lol.
Am I doing something wrong or is this by design?
I don't know if this in it itself justifies additional tooling for you, but just to put it out there in case it is useful:
If you're open to solutions from the Atlassian Marketplace, this would work as expected using the app that my team and I are working on: JXL for Jira.
JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. It also comes with a range of advanced features - including support for (configurable) issue hierarchies, issue grouping by any issue field(s), sum-ups, or conditional formatting - and works across any number of projects.
Plus, as you filter your issues, the active issue hierarchy is maintained, e.g. like so:
Any questions just let me know!
Best,
Hannes
Welcome @Yousif Hassan
This is by design. Whenever filtering is used, the list of issue turns into a list and all the expanding& collapsing is disabled.
You'll see this message when you try to expand all.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Benjamin - do you know what the reason is? Why is this the case - seems inconsistent?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.