No — plain Jira Software still has no free, native way to add a level above Epic that shows up anywhere you’d actually look for it. Checked directly against Atlassian’s own docs as of the 2026 Summer Release: a Premium or Enterprise admin can create a level-2 work type above Epic, but only in company-managed projects, and once created it’s still boxed into Plans — Timeline, boards, and the backlog panel don’t lay it out as a hierarchy. Two long-running Atlassian Community threads run into exactly this. This page is about native Jira Software; it is not about Jira Align, a separate product with its own hierarchy — more on that distinction below.
What people are actually stuck on
Two threads carry this, both still live on the Atlassian Community, re-checked directly today:
- “Additional Work Type Hierarchy Level” — 3,074 views. The asker wanted to insert a level above Epic (moving Epic to level 2, with a new “Feature” type as its parent) on Jira Cloud Premium. The accepted answer, from a Community Champion: team-managed projects are hard-capped at three hierarchy levels, so getting above Epic requires modifying the global Issue Type Hierarchy to add a level-2 type in a company-managed project, then linking a team-managed project’s Epics up to it through Plans. The asker got it working — but only by rebuilding the affected project as company-managed and using Plans to bridge the two.
- “Hierarchy level above EPICS — cannot use it even with premium” — 1,022 views. The asker had Premium and created a custom “Master Epic” work type above Epic, then couldn’t get it into their agile space or the Timeline view at all. The reply that settled it: “the Timeline specific view will apply only to the Epic level and below.” Premium didn’t fail here — it just doesn’t reach that far.
Both threads end the same way this page will: a real, narrow capability exists, and it stops well short of “see your hierarchy above Epic the way you see it below Epic.”
Not Jira Align — a different product
Worth stating plainly, because both terms use the word “hierarchy” and both come up for “level above epic” searches. Jira Align is a separate, standalone Atlassian product for enterprise SAFe-style portfolio planning, sold and licensed on its own, with two of its own hierarchies — an org hierarchy (Portfolio → Solution → Program → Team) and a six-level work hierarchy (Strategy → Theme → Epic → Capability → Feature → Story) that Jira Align maintains independently of plain Jira issue types. See Jira Align hierarchy levels for that system in full.
This page is about Jira Software — the product most people mean when they say “Jira” — and its native issue-type hierarchy (Epic → Story/Task → Sub-task, extendable by one level with Premium). Different product, different buyer, and a very different price point: Jira Align is an enterprise sale; the Premium tier discussed below is a per-seat upgrade on the Jira most teams already run. If you searched this exact phrase because someone mentioned Align, start at What is Jira Align? instead.
Does the 2026 Summer Release change this? Checked directly — no
Jira’s 2026 Summer Release is real and it touches hierarchy, which makes it worth checking carefully rather than assuming. Per Atlassian’s own release blog and the Community announcement thread, the release merged the old List and All Work views into one List view — “search with Jira Query or natural language, see parent/child hierarchy, edit inline, and save custom views” — and shipped formula fields that calculate values on a single work item.
Neither is described anywhere in Atlassian’s own material as reaching above Epic. The List view’s new “Show Hierarchy” toggle nests child items under parents with expand/collapse — every example and every Community thread about it (including a 666-view thread confirming how to turn it on) is about Epic-down nesting, not Epic-up. And Atlassian’s own configuration page for custom hierarchy levels states plainly that reordering levels in a Plan “won’t change the structure of your Jira work types” — i.e., that configuration is scoped to the Plan you’re looking at, not projected out into List view, boards, or backlog.
Verdict: the gap is still fully open. The Summer Release made Epic-and-below easier to browse in one unified view. It did nothing, per Atlassian’s own docs, to the wall above Epic.
What Premium’s Plans actually lets you do — and where it stops
Set aside the release for a moment and look at the steady-state feature, because it’s genuinely more capable than “no.” Per Atlassian’s own Jira Cloud KB on custom work type hierarchies, a Premium or Enterprise admin can:
- Create a new work type (commonly “Initiative”) in the Global Issue Type Hierarchy at level 2, above Epic.
- Associate it with a company-managed project’s issue type scheme.
- Use it as a parent for Epics — and per the KB, this reflects in a few ordinary places, including the Epic dropdown and Epic panel in Backlog, so you can actually assign the parent link without leaving the backlog.
That’s real, and it’s the mechanism the 3,074-view thread’s asker used successfully. But two hard limits confirmed directly by the sources above bound it:
- Company-managed projects only. Team-managed projects are capped at three hierarchy levels total (Sub-task, Story/Task, Epic) and cannot go higher, per the accepted answer in that same thread.
- Laid-out visibility stays inside Plans. The parent link exists globally, but seeing the Initiative-level rows laid out as a hierarchy — the actual point of having a hierarchy — is confirmed to be Plans-only. The 1,022-view thread’s asker had Premium, created the type correctly, and still couldn’t get it into their Timeline view, because (per the accepted answer) “the Timeline specific view will apply only to the Epic level and below.” You have to open a Plan specifically to see the extra level at all — the same Premium/Enterprise-gated surface, a second time.
The free-tier workaround: labels, components, “themes”
If you’re not on Premium, or you’re on a team-managed project that structurally can’t go above three levels, the honest fallback — described by Atlassian’s own KB as the no-Premium option — is a tag, not a hierarchy: create ordinary issues (or use a label, component, or custom field) named “Initiative” or “Theme,” and link or tag Epics to them. Jira does not treat this as a parent-child relationship for reporting — no automatic rollups, nothing enforcing one theme per Epic, and any total across it needs the same kind of hand-built automation rule covered on summing story points from children to a parent. It’s free, it’s immediate, and it is genuinely a grouping label wearing a hierarchy’s clothes.
Marketplace apps that add a real level above Epic
Three Marketplace apps build their own hierarchy layer independent of Jira’s native issue-type config — which is the actual advantage over both the Premium path and the label workaround, since none of them require a Premium seat to show a level above Epic:
- Structure, by Tempo (formerly ALM Works — Crosstown Tech’s founder was Structure Cloud’s PM for five-plus years to Jan 2025, noted for transparency, not as an endorsement). Per Tempo’s own comparison, it builds “custom, reusable structures that pull issues from many projects,” commonly modeled as Initiative → Epic → Story, without touching Jira’s own hierarchy settings.
- BigPicture, which the same comparison describes as offering “multi-level hierarchies” and “Portfolio structures” as its own organizational model, also independent of native Jira config.
- Hierarchy for Jira (Adaptavist), whose Marketplace listing advertises the ability to “link work items to visualise levels above and below epics” in a nested tree view.
Each is a separate purchase and a separate tool to maintain — not a Jira setting you flip — but all three sidestep the Premium requirement and the Plans-only visibility limit at once.
The honest summary
| Path | Real level above Epic? | Visible outside Plans? | Cost |
|---|---|---|---|
| Team-managed project | No — hard-capped at 3 levels | — | Free |
| Company-managed + Global Issue Type Hierarchy | Yes | No — Timeline/List/boards stay Epic-and-below; only inside a Plan | Premium/Enterprise seat |
| Label/component/custom field “theme” | No — a tag, not a hierarchy | Yes, but it’s just a filter | Free |
| Marketplace app (Structure, BigPicture, Hierarchy for Jira) | Yes, in the app’s own layer | Yes, inside that app | Separate purchase |
| OneView | Yes, if Jira already has the level (Premium) — surfaced, not created | Yes — an ordinary grid, no Plan required | See below |
What OneView does instead
OneView signs in with your real Atlassian account and reads whatever hierarchy your Jira site actually has — including a Premium-configured Initiative level, or any custom level beyond it — and lays it out as a real, groupable rung in an ordinary grid, across as many projects as your work spans. It doesn’t get around Atlassian’s Premium gate to create a level that doesn’t exist (nobody but Jira admin settings can do that); what it fixes is the second half of the problem this page just documented: once you have that level, you shouldn’t need to open a specific Plan’s Timeline just to see it. If Premium isn’t in the picture at all, OneView’s arbitrary grouping does the same job as the label workaround above — group Epics by any field you already have — just inside a grid that also handles the rollups and cross-project scope, rather than a label with no structure behind it. Start a free trial and point it at a project that already has an Initiative level configured.
Related reading
The hierarchy question is one axis of a bigger pattern: Jira’s shape doesn’t always match how the work is actually structured. If the wall you’re hitting is a number rather than a level, see summing story points from children to a parent — same underlying limitation (a field or a view Jira’s native surfaces don’t extend past), applied to rollups instead of hierarchy depth. And if “hierarchy” brought you here because of Jira Align rather than plain Jira, Jira Align hierarchy levels covers that separate product’s own two hierarchies in full. If you’re weighing Structure against Plans specifically as the way to get above Epic, Structure vs Advanced Roadmaps (Plans) in Jira covers how those two compare and whether you need both. And if the hierarchy you’re missing is Epic-over-Story rather than anything above Epic — specifically on the Backlog screen, where only sub-tasks nest — see parent/child hierarchy in the Jira Backlog, which covers the same Epics-panel workaround from the other direction.