issuetype = Epic:issuetype = Epic OR parent is not EMPTY) and ordering by Hierarchy (ORDER BY cf[number] ASC): --> I replaced the real number by "number" only for this threadHi @Lena Wong, known limitation, and attempt 1 is where it shows. Filter to issuetype = Epic and the hierarchy stops rendering, which is JRACLOUD-94328, Gathering Interest, 29 votes. Attempt 2 gets the arrows back by pulling every child into scope, so each child then takes a root row of its own. Same reason Collapse all can't touch the orphan Xray tests. No JQL and no field ordering closes that gap.
On Premium or Enterprise, build a plan over the project. Filters menu, Work types set to Epic, then turn on Show full hierarchy. Going by the docs that pulls the children back in as expandable rows even though they don't match, and an orphan Xray test matches nothing, so it stays out of the tree.
The project's Timeline tab gets closest without Premium. Children nest under their parents there, and a child with no parent doesn't render at all.
On both routes though, a Test with an Epic as its parent still shows when you expand that Epic.
Hello @Lena Wong,
the plan and Timeline routes that @Gabriela - LeanZero laid out are the closest you'll get natively as far as I know. I'd just add an option for the last gap: on both of those routes, a Test that has an Epic as its parent still shows up once you expand the Epic.
If you're open to apps from the Atlassian Marketplace, JXL for Jira handles the whole requirement in one view:

Disclosure: I work for the team that builds JXL.
Best, Paul
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.