I need to create tree view in filter and dashboard

[rayyan_siddiqui]

I need to create tree view in filter and dashboard, 

Epic - Progress

-Story - progress

--Task - progress

---Subtask - progress

[Lalithesh]

Hi @rayyan_siddiqui 

Welcome to the Atlassian community!

In Jira Cloud, there is no native dashboard gadget that displays a hierarchical tree. If you're on Jira Premium or above tier you can use Plans (formerly, Advanced roadmaps).

Or you can use 3rd party add-ons like 'Structure by Tempo' to built this

Cheers!

[Ivan Manolov _Appfire_]

Hello @rayyan_siddiqui,

One detail in your sketch is worth pulling out, because it explains why none of the native views will quite match it: the four levels you drew don't exist in Jira's hierarchy.

Jira ships with Epic at level 1, Story at level 0, and subtasks below that. Standard work types are all added at the story level, so Task and Story are siblings, not parent and child. A Task cannot sit under a Story natively, which means no native tree can render Epic > Story > Task > Sub-task as drawn.

Two ways forward:

If you have Premium or Enterprise. You can add levels above epic, not between story and subtask. An admin creates the work type, adds it to the work type scheme, and associates it with a new hierarchy level. That gets you a genuine four-level tree, for example Initiative > Epic > Story > Sub-task, in Plans. One easy thing to miss: the Parent field has to be on your work items for those relationships to show up on the work items themselves.

If you're on Free or Standard. Treat it as three levels and use the List view's hierarchy or the project Timeline, where Story and Task both nest directly under the Epic.

Worth deciding what "progress" means before you build any of it, since count of children, story points done and time-based progress give different numbers for the same tree.

Best,

Ivan

[Ivan Manolov _Appfire_]

Following up on my earlier answer, @rayyan_siddiqui: if you want the four levels exactly as you drew them, including on a dashboard, and you're open to solutions from the Atlassian Marketplace, that is what the app my team and I work on, JXL for Jira, is built for.

JXL is a spreadsheet/table view for your Jira data, and its custom structures let you define the levels yourself. Each level picks its own work types, and the parent relationship can come from the Parent field or from work item links, which is how you get a Task nested under a Story without Jira having such a level. Sum-ups then give you a value on every parent row, whether that's story point totals, a status distribution, or a done percentage, so the progress column appears at each level of the tree rather than only on epics.

Sheets also come with a dashboard gadget, so you can drop a saved view of this tree straight onto a Jira dashboard.

Any questions, just ask.

All the best,

Ivan

[Anderson JS]

Heya @rayyan_siddiqui 

Native Jira dashboards can't render a nested tree, unfortunately — the Filter Results gadget always shows a flat list, even if your filter contains the whole hierarchy. But there are a few ways to get close, depending on what you're on:

1. Jira Premium — Plans (Advanced Roadmaps)

This is the closest thing to exactly what you described: an expandable Epic → Story → Task → Subtask tree with a progress bar rolled up at each level.

Create a plan scoped to your project or a saved filter, set the hierarchy range to include subtasks, and enable the Progress column. It lives outside the dashboard, but you can share a view link with the team.

Docs: https://support.atlassian.com/jira-software-cloud/docs/what-are-plans-in-jira-software/

2. The project List view (free plans included)

In newer Jira Cloud projects, the List view has a hierarchy toggle that nests child issues under their parents, so you get the tree with status/progress fields visible. Again, viewable per project rather than embeddable in a dashboard.

3. Gathering the tree in JQL

For the filter itself, you can pull one epic's whole tree with:

parentEpic = ABC-1 OR key = ABC-1 ORDER BY parent, rank

Sorting by parent at least keeps children grouped under their parents in the flat list, which some teams find readable enough.

4. A rollup table on the dashboard

If a rollup number is enough (rather than the tree structure), the Two Dimensional Filter Statistics gadget with rows = Epic Link (or Parent) and columns = Status gives you a compact per-epic progress table.

---

If you need the actual expandable tree with progress bars inside a dashboard gadget, that gap is only filled by Marketplace apps — search the Marketplace for "hierarchy" or "issue tree" gadgets and check they support your hierarchy depth including subtasks.

Thanks,

Anderson

[Danut M _StonikByte_]

Hi @rayyan_siddiqui, 

You can get a hierarchical view in the List tab of the spaces/project. 

  

If you want this in a dashboard, the solution would be to use a plugin from Atlassian Marketplace, because Jira does not offer such gadget.

In case you want to use a plugin, our Great Gadgets app offers a Work Breakdown Structure (WBS) gadget that is capable to display the issues hierarchically, in form of Initiatives > Epics > Stories > Subtasks, as a tree view or as a hierarchical list.

All you have to do is to configure it will a filter that returns the issues to be displayed, and it does the hierarchical grouping for you.

Hope this helps. 

Danut.

[Andrey - Guenov Labs]

Two things are being conflated here, and separating them makes this much easier to solve.

1. Hierarchy. It's true there's no dashboard gadget that renders a tree — dashboard gadgets are built on filters, and filter results are a flat list by design. But Jira does render hierarchy natively in a few places:

• Plans (Premium/Enterprise) is the real answer if you have it. Full Epic → Story → Subtask tree, expandable, with progress bars and a saveable view.
• Project Timeline (Free and up) gives Epic → child in an expandable tree with progress bars. Less flexible than Plans, but free and often enough.
• The work item view shows a Child work items panel with a completion bar on any parent.

None of these live on a dashboard, which is the real constraint you're hitting.

2. Progress — and this is the part that quietly breaks. "Progress" isn't one thing in Jira, and the different views don't compute it the same way. Decide which you mean before you build anything:

• By count of children done — simple, and what the Timeline and Child items panel use. Treats a two-hour subtask and a two-week one as equal.
• By story points rolled up — meaningful, but only if you estimate consistently at one level. Mixed estimation across Epic/Story/Task produces confident-looking nonsense.
• By time tracking — accurate only if people actually log work.

Most "why doesn't my rollup match reality" problems trace back to this, not to the tree.

If you're stuck on a dashboard specifically, the honest native workaround is the Filter Results gadget with a JQL that scopes to one epic's subtree (parentEpic = ABC-123) and a sort that groups children under parents — you get the right items with the right progress fields as columns, just without the indentation. Not a tree, but it puts the data on the dashboard, which is usually the actual need.

If the indented tree is genuinely non-negotiable and Plans isn't available on your plan, that's the point at which Marketplace apps are worth looking at — but I'd try Plans or the Timeline first, since one of them covers most of what people mean by this.

[Habib__Plugio__]

Hi @rayyan_siddiqui 

This exact view — the tree with progress at every level — doesn't exist natively: saved filters always render flat lists and dashboards have no tree gadget. Plans (Premium) comes closest but lives outside filters and dashboards.

Full disclosure — I'm the developer of Plugio Suite.

Its Hierarchy widget was built for precisely this. Here's what it looks like on a dashboard:

What it does, against your sketch:

• The full tree, expandable: Epic → Story/Task → Sub-task, each level collapsible, keys click through to the issue.
• Progress at every level that has children — the epic rolls up its whole subtree, a story shows its own sub-task progress bar.
• No estimates required: progress can be plain issue count, or Sum of Story Points if your team estimates — both status-category based (Done / In Progress / To Do in Jira's own colours).
• Columns are yours to compose: the row's own fields (Status, Assignee, dates) next to roll-up value columns, each shown as a bar, dots (one square per item), a fraction or a number — the screenshot mixes several.
• Sub-tasks count the way your team means them: as real work (lowest-level roll-up) or as a checklist that shows but never enters the numbers.
• One filter bar drives it: the dashboard's period, assignee, priority filters apply to the tree — an epic that shows always brings its whole tree, so a branch is never cut in half.
• The dashboard embeds into a native Jira dashboard as a single gadget, or shares as a full page.

[Laura Marin - Millarum]

If you're looking for a native solution, Jira List has this implemented awhere you can see the tree view and the status of all work items as follows:

However if you're looking not just for the status of the items by themself but a cumulative status from their child work items, Jira offer the Epic progress inside the Issue view, but to see it in a tree view I think it's not something natively available.

Full disclosure, I'm part of the team behind Millarum Dashboards

If you're open for a third party solution, our list widget that by the way can be updated dynamically by the slicer widget, can show the status of the child work items within the tree view.

 

[Nikola Perisic]

Hi @rayyan_siddiqui 

For Jira, tree view currently doesn't exist. It does exist in the Jira product discovery. You might want to take a look at this: https://community.atlassian.com/forums/Jira-questions/Tree-of-tasks-How-can-I-do-it/qaq-p/2525832