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,299,995
Community Members
 
Community Events
165
Community Groups

How to Change the Issue Types Hierarchy in advancenced roadmaps

Hi Team,

I want to create an hierarchy of 

1) Epic

2) New Feature

3) Story

For New Feature ,Epic should be the Parent. For Story New Feature should be the Parent.

All Stories should be created under New Feature only.

Please help me with this Scenario in Jira Cloud.

2 answers

1 accepted

0 votes
Answer accepted
Curt Holley Community Leader Sep 29, 2021

Hi @Deepika.Kanaparthi 

Welcome to the Atlassian community.

It is not possible to insert a hieratically level in-between Story and Epic, only above Epic.

You can have Features at the same level as Stories, but that doesn't sound like what you want.

I would suggest that you use Jira epics as your Features and create a SAFe Epic or Initiative issue type that you use as the upper level of the hierarchy. To link the Epics up to that upper level ensure that you add the Parent link field to your epics. This field works just like the Epic link field works between stories and Epics.

See here for details: Solved: Adding a Parent Link to an EPIC issue (atlassian.com)

0 votes
Rohan Swami Atlassian Team Sep 29, 2021

@Deepika.Kanaparthi @Curt Holley I'm happy to say that we are actively building a solution to this problem, shipping in 2022 Q2-Q3 calendar year. Premium customers will be able to implement a hierarchy of:

1. Epic
2. Feature
3. Story

We've put this in the public roadmap here as Flexible naming of Epics. https://www.atlassian.com/roadmap/cloud?status=inTheWorks&

Use your preferred terminology for Epics to create consistent - and SAFe compatible - naming in Jira Software.

As we get closer to release I'll be able to share details of the solution.

Curt Holley Community Leader Sep 29, 2021

Excellent news @Rohan Swami !!

So I take it the hierarchy stays the same, it is just the ability to (globally, in a cloud instance???) rename Epic to Feature (or whatever) and all other functionality of the current hierarchy (Initiative/Epic/Story/sub-task) would remain the same? Including the Epic and Parent link fields....is that right?

Rohan Swami Atlassian Team Sep 29, 2021

Yep that's the plan - Epics can be renamed to Features, and users can create an a new issue type called Epic to parent them.

We intend to combine some of the functionality around epic-link and parent-link without losing any capabilities.

Like Ulrich Kone likes this

Hello @Rohan Swami 

This is exactly what we did.

But for now on, the parent link and the epic link are not taken into account in the dependencies.

Rohan Swami Atlassian Team Jun 28, 2022

Hi @Ulrich Kone this functionality hasn't shipped yet. We have recently shared more details about our plans, you can find them here https://support.atlassian.com/jira-software-cloud/docs/upcoming-changes-epic-link-replaced-with-parent/

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Confluence

An update on Confluence Cloud customer feedback – June 2022

Hi everyone, We’re always looking at how to improve Confluence and customer feedback plays an important role in making sure we're investing in the areas that will bring the most value to the most c...

336 views 2 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you