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; } } }

How to Change the Issue Types Hierarchy in advancenced roadmaps

Deepika.Kanaparthi

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.

Comments

Curt Holley

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)

Rohan Swami

@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

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

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.

Ulrich Kone_wqg3nu

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.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

advanced-roadmaps