Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,363,188
Community Members
 
Community Events
168
Community Groups

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

Hi @CARLOS EMILIO CASTILLA MAR 

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

@CARLOS EMILIO CASTILLA MAR -

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.

Hi @CARLOS EMILIO CASTILLA MAR ,


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,
Iryna
Anova Apps Products Team

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events