No. The Jira Backlog nests exactly one relationship — a Sub-task under its parent issue — and nothing else. A Community Champion answering this question directly, in a thread with 1,954 views, put it plainly: “The backlog will show nesting of child issues only for sub-tasks under their parent issue. No other parent/child relationship nesting can be displayed in the Backlog issue list.” Epics, Stories, and Tasks all sit in the same flat, rankable list. That’s not a missing setting — it’s the tradeoff the Backlog makes to stay a single drag-and-drop priority order.
The question, asked directly
“How do I get my backlog to display in parent/child format” is the highest-view unanswered-in-spirit thread on this exact topic — 1,954 views as of this writing. The asker’s setup is the common one: “The work items in my backlog appear to be a dump of all Epics Stories Tasks and Subtasks, how can I get the backlog to display in a usable parent/child format?”
The answer that landed, from a Community Champion, has three parts:
- Sub-tasks nest. Nothing else does. The Backlog shows a Sub-task under its parent issue automatically. Epic-over-Story, Story-over-Task, or anything above Epic doesn’t nest in the Backlog at all, regardless of settings.
- Epic-over-Story nesting exists — in a different view. The basic Timeline view, inside a single Jira Software project, does lay Epics out with their child Stories underneath. That’s the native answer to “where do I see this nested,” just not on the Backlog screen.
- Above Epic, or across projects, needs Plans. Extending the hierarchy further requires an Advanced Roadmaps Plan — a Premium/Enterprise feature with its own separate Timeline.
Why the Backlog is built this way
This isn’t an oversight; it’s the Backlog’s whole reason for existing. Per Atlassian’s own guidance on customizing the board and backlog view, the Backlog is a single ranked list you reorder by dragging — every issue on it has one position, and that position is the plan for what gets worked next. If Epics visually contained their Stories the way a folder contains files, ranking would fragment: you could reorder within a branch but not slide a Story from one Epic ahead of a Task under a different Epic, which is exactly the cross-cutting reprioritization sprint planning needs. Sub-tasks are the one thing exempted, because a Sub-task doesn’t carry its own backlog rank at all — it just rides along with its parent’s position, so nesting it costs the ranking model nothing.
The same design tension shows up one view over. In “Jira List view - keeping the hierarchy tree while having an active filter” (1,893 views), the accepted answer claims the All Work view keeps its hierarchy tree intact even with a filter applied — Walter Buggenhout wrote “the All Work view also shows your work in a hierarchy, even when you apply filters there.” A later reply from Olivier Didrit directly disputes that: “On my side, the hierarchy is also no more shown in the All Work as soon as you apply filters.” Nobody in the thread resolves the disagreement, and a moderator points instead to an open feature request (JWMCLOUD-698) plus Plans as the current fallback. Worth reading honestly rather than taking the accepted-answer tag at face value: hierarchy-versus-filter is a live pain point across Jira’s list-style views, not a solved problem confined to the Backlog.
Does the 2026 Summer Release change this?
Partly, but not for the Backlog. Jira’s 2026 Summer Release is real and it did ship native parent/child hierarchy — it merged the old List and All Work views into one List view that lets you “search with Jira Query or natural language, see parent/child hierarchy, edit inline, and save custom views,” per Atlassian’s own release post. The Community announcement thread confirms the same List view rollout, general availability by end of August 2026.
That’s a genuine upgrade — but to a different screen. List view is a flat table with optional row-level nesting and expand/collapse; it isn’t the Backlog and doesn’t carry the Backlog’s drag-to-rank behavior. What the release did change on the Backlog itself is speed and consistency: Atlassian’s release material describes rebuilt boards and backlogs running “up to 22% faster,” with swimlane and sub-task behavior now consistent between software and business spaces — nothing about Epic or Story nesting. A Jira Backlog opened today shows exactly the same sub-task-only nesting it showed before the release.
The two real workarounds
Neither is nesting, but both give you parent context without leaving the Backlog:
Turn on the Epics panel. Per Atlassian’s own customization docs, the Backlog has a toggleable Epics panel (keyboard shortcut E) that lists every Epic down the left side; clicking one filters the Backlog to just that Epic’s issues. It’s a filter, not a view of the whole backlog with structure — turn it on and you lose the single ranked list across all Epics, which is the thing you opened the Backlog to use in the first place. The same docs also cover swimlanes: expanding them shows sub-tasks inline, collapsing shows story-level items only — the one nesting control the Backlog actually has.
Show the parent on each card. A Community thread, “Display Parent on story/bug/task cards in Scrum Board’s backlog view”, landed on adding the Parent Link field to the card layout so each issue shows its Epic as a label — a flat tag, not a nested tree. The thread also surfaces the generic Linked Issues field as a fallback for non-standard parent relationships, with a caveat from a Community expert: “You can’t configure it to show issues of only a particular link type,” so it shows every link on the card, not just the parent.
The honest summary
| What you want | Native Jira | Where |
|---|---|---|
| Sub-task nested under its parent | Yes, automatic | Backlog |
| Epic nested over its Stories | Yes | Timeline (per project) |
| Hierarchy above Epic, or across projects | Yes, Premium/Enterprise | Advanced Roadmaps Plan |
| Epic/Story hierarchy on the Backlog itself | No | — |
| Parent visible (not nested) on a Backlog card | Yes, via Parent Link field | Backlog |
| Backlog filtered to one Epic | Yes, via Epics panel | Backlog |
If your search brought you here hoping for a Backlog display toggle, there isn’t one — the Backlog’s whole model is a flat ranked list, sub-tasks are the sole exception, and Epic/Story structure lives one screen over, in Timeline or Plans.
What OneView does instead
OneView reads your real Atlassian projects and lets you add the hierarchy levels your organization actually uses — nest Epics over their children, roll story points and estimates up to the parent, group by any field — as one grid, not a screen you have to switch to. It is not a replacement for the Backlog’s ranking. There’s no drag-to-rank in OneView; it doesn’t set sprint priority the way the Backlog does. What it solves is the display gap this page is about — seeing the hierarchy at all — not the planning function the Backlog exists for. If what you need is to actually reorder next sprint’s work, that’s still the Backlog’s job. Start a free trial to see your own hierarchy laid out.
Related reading
This page is about the Backlog specifically — the ranked, prioritizable list, where only sub-tasks nest. If your actual question is about seeing Epic-over-Story structure anywhere in Jira, including above Epic, see a hierarchy level above Epic in Jira, which covers Timeline, Plans, and what a custom Initiative-level work type does and doesn’t show — including the same Epics panel this page describes. And if the gap you’re actually hitting is a dashboard rather than a planning list — you want status or sprint progress rolled up across projects, not a ranked backlog — see a Jira dashboard across multiple projects, which runs into the same “the new List/Summer-release features solved a different screen” pattern this page does.