Hello Atlassian Support Team, We are using Jira Cloud and want to establish a delivery hierarchy that scales well across teams and supports both portfolio-level planning and team-level execution. Our target hierarchy is: * Epic → contains multiple Features * Feature → contains multiple User Stories / Tasks * Completion of multiple Features rolls up to complete an Epic Currently, Jira natively supports Epic → Story, but we are looking for guidance on the best and supported way to introduce a Feature layer between Epic and Story. Could you please advise on the following: * Recommended approach in Jira Cloud to model this hierarchy, including guidance on: * Custom issue types with parent–child relationships * Using Advanced Roadmaps hierarchy levels * Issue linking versus native parent/child relationships * Any other supported or recommended patterns * Feasibility without Jira Align: * Can this structure be implemented without Jira Align? * If so, which Jira plans (Standard vs Premium) are required? * Progress, status, and reporting roll-ups: * How story-level progress can roll up to Features * How Feature-level progress can roll up to Epics * Any native reporting or roadmap capabilities that support this * Limitations, trade-offs, and best practices: * Known constraints in Jira Cloud for multi-level hierarchies * Reporting or governance considerations * Recommendations for keeping the setup low-maintenance and scalable over time Our goal is a clean, sustainable model that avoids excessive customisation while still providing clear visibility from execution through to portfolio planning. Thanks in advance for your guidance. Kind regards, Kush Sharma

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Guidance on implementing Epic → Feature → Story hierarchy in Jira Cloud

Kush Sharma_fgqmyi

Hello Atlassian Support Team,

We are using Jira Cloud and want to establish a delivery hierarchy that scales well across teams and supports both portfolio-level planning and team-level execution.

Our target hierarchy is:

Epic
→ contains multiple Features
Feature
→ contains multiple User Stories / Tasks
Completion of multiple Features rolls up to complete an Epic

Currently, Jira natively supports Epic → Story, but we are looking for guidance on the best and supported way to introduce a Feature layer between Epic and Story.

Could you please advise on the following:

Recommended approach in Jira Cloud to model this hierarchy, including guidance on:
- Custom issue types with parent–child relationships
- Using Advanced Roadmaps hierarchy levels
- Issue linking versus native parent/child relationships
- Any other supported or recommended patterns
Feasibility without Jira Align:
- Can this structure be implemented without Jira Align?
- If so, which Jira plans (Standard vs Premium) are required?
Progress, status, and reporting roll-ups:
- How story-level progress can roll up to Features
- How Feature-level progress can roll up to Epics
- Any native reporting or roadmap capabilities that support this
Limitations, trade-offs, and best practices:
- Known constraints in Jira Cloud for multi-level hierarchies
- Reporting or governance considerations
- Recommendations for keeping the setup low-maintenance and scalable over time

Our goal is a clean, sustainable model that avoids excessive customisation while still providing clear visibility from execution through to portfolio planning.

Thanks in advance for your guidance.

Kind regards,
Kush Sharma

Accepted answers

Marc -Devoteam-

Hi @Kush Sharma

There is no option to add layers between Epic level and Story level.

What you can do is rename the Epic to Feature and then add a new work type, with Name Epic, add this new work type above Feature.

This new work type will behave as a normal work type, as there can only be one work type based on how an ootb Epic work type functions.

Then you can use ootb Plans function, if your subscription matches this.

All comments

Marc -Devoteam-

Hi @Kush Sharma

There is no option to add layers between Epic level and Story level.

What you can do is rename the Epic to Feature and then add a new work type, with Name Epic, add this new work type above Feature.

This new work type will behave as a normal work type, as there can only be one work type based on how an ootb Epic work type functions.

Then you can use ootb Plans function, if your subscription matches this.

Kush Sharma_fgqmyi

Thanks Marc for the clarification.

Just to confirm and close this out, could you please confirm the following:

With the proposed setup (renaming Epic → Feature and introducing a new Epic work type above it), will we be able to achieve a true Epic → Feature → User Story hierarchy in Jira Cloud?
- And does this require Jira Premium / Plans to function as intended?
Will Plans support progress roll-ups from:
- User Stories → Features
- Features → Epics
Are there any known risks or limitations with renaming the Epic issue type (e.g. impact on reporting, automation rules, or marketplace apps)?

Thanks for your confirmation so we can proceed with confidence.

Thanks,

Kush Sharma

Karan Sachdev

Hey @Kush Sharma ,

Good day!

I just noticed in the details of this post that you're on a Standard plan. Is that correct?

If so, I'm sorry but we don't have a way to add hierarchy levels. The default hierarchy remains as is:

Epic (Level 1)

Story/Task/bug (Level 0)

Sub-tasks (Level -1).

If you're on a Premium plan, the approach suggested by @Marc -Devoteam- will fulfil your requirement.

Thanks!

Marc -Devoteam-

Hi @Kush Sharma

Yes, this does require Plans, so a premium subscription is required.
Yes
No, not that I'm aware of.

If you are not on a premium subscription, my solution won't work ootb.

You can achieve the same, but then you will need to look at 3rd party solution from the marketplace, like;

Strucutre
BigPicture
etc..

John Funk

Hi @Kush Sharma - the risk is that the new hierarchy applies to your ENTIRE Jira instance - meaning ALL Spaces/Projects. So if you have some Spaces that currently use the Epic as the level above Stories or Tasks, that will change for them.

Joshua Brock _ Seibert Group_ GmbH

@Kush Sharma

Great question, and it looks like you have a handful of suggestions to work with... if I might, I'll just add one more for consideration: our tool Agile Hive.

To help give you a more comprehensive way to view and manage cross-team work, manage dependencies, PI planning, and all aspects of sprint and iteration management, team up to portfolio management, team and ART planning boards.

In full transparency, I am a content writer for Agile Hive, and our comprehensive solution integrates fully with Jira Cloud and Data Center. Please feel free to give it a look and reach out for a demo, or certainly reach out here, whichever works best.

Again, welcome - you'll find the community to be extremely helpful!

Joshua
Content and Technical Writer
Agile Hive (Seibert Group, GmbH)

Olga Cheban _TitanApps_

hi @Kush Sharma !

Overall, Jira doesn't allow you to insert additional hierarchy levels below Epic.

With Jira Plans (Premium subscription required), you can add custom levels above Epic, but not below.

So your options are workarounds with renaming work types. One option is what Marc described: to rename the Epic to Feature and then add a new work type, name it Epic, and add this new work type above Feature. For this, you will need access to Jira Plans (Premium subscription required). For more details on how to configure a custom Jira hierarchy, please refer to my article Advanced Roadmaps Hierarchy Configuration Guide 2026.

Another option is to keep the Epic as is, add a new work type at the Task/Story/Bug level and call it Feature, and use subtasks under that Feature instead of Stories. In this case, the naming might be a bit confusing, since your Stories will be managed in Subtasks and called Subtasks. On the upside, you don't need a Premium subscription to use this workaround.

I hope this helps!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud