Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Is it possible to include Feature between Epic and Story?

We are using Jira Data Center version 7.13 and Advanced Roadmaps. We want to introduce Safe Hierarchy. Theme--> Epic -->Capability  --> Feature --> Story

Finally we want to start creating plans/programs in advanced roadmaps to display the breaking down hierarchy Theme--> Epic -->Capability  --> Feature --> Story


3 answers

1 vote
Henri Seymour _Easy Agile_
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
May 17, 2021


The Epic -> [Story/Task/Bug] -> Sub-task hierarchy in Jira is fixed; unless you find an app that suits your needs, you won't be able to add other steps in that hierarchy or change the order. 

You might be interested in some of the previous discussions here about this problem to see how other people have approached this: 

Kind regards, 
Henri Seymour, Developer @ Easy Agile  

1 vote
Joseph Chung Yin
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 17, 2021


Welcome to the Community.  In Jira Hierarchy setup (provided by AR), you would not be able to change Story rollup to EPIC (i.e. adding Feature to be the parent of Story).  

EPIC > Story > Subtask is the based default Jira scheme.  You can create Feature, Capability to roll up to EPIC just like the Story issue type.  However you cannot change the default Jira scheme even with the Hierarchy functionality to add new parents below EPICs.

The possible options is to utilize "Component/s" or "Release" to represent your feature/capability and then  associate them to your Stories.  In AR, you can use them to group your issues.

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

0 votes
Iryna Ihnatiuk _Appfire_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 20, 2021


You can meet your needs using SAFE Epic to Feature Translator app with Advanced Roadmaps. 

SAFE Epic to Feature Translator helps you to change native Jira naming "epic" into "feature" (or whatever you want) everywhere in your Jira instance and saves native hierarchy: Feature (former Epic) → Story.

The only thing - you have to create a new issue type with some other name like "Portfolio Epic" or "Epic1" or anything else rather than exactly "Epic". Otherwise, there will be conflicts in Jira as it will consider them as duplicates.

SAFE issue hierarchy.png

Feel free to reach out support team if you need further information.

Kind Regards,
Anova Apps Products Team

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events