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 set SAFe structure of 04 level hierarchy (Epics - Features - Stories - Tasks) in JIRA ?

Akshay Mishra_4f5xm7

Hi All,

We are a startup with only 03 devs and want to use JIRA free tier currently for some time - until we make money and upgrade.

Currently our project plan in excel has 04 levels of hierarchy as SAFe - "Epics - Features - Stories - Tasks". Jira by default supports only 03 levels - "Epics - Strories - Subtasks".

We have 50+ features, 250+ stories and 1500+ tasks - so flattening this structure is not very straight forward.

How do I fit these 04 levels in my JIRA free tier ?
Renaming these levels is possible but flattening them is difficult.

Thanks in advance.

Accepted answers

Marc -Devoteam-

Hi @Akshay Mishra

Welcome to the community.

You will need to adjust the hierarchy, but keep in mind, there can't be a level between Epic and Story and you can only have one isue type behaving as Epic.

So if you require a level above the current Epic and need that to be Epic, rename the Epic issue type/work item to lets say Feature and create a new issue type that you will call Epic.

In the Work Item section of Jira administration you will find the Work Item hierarchy, there you can place the new Epic above the renamed Epic, now Feature.

The Feature will have the ootb Epic functionality and the new Epic is just an work item like Story or Task

All comments

Marc -Devoteam-

Hi @Akshay Mishra

Welcome to the community.

You will need to adjust the hierarchy, but keep in mind, there can't be a level between Epic and Story and you can only have one isue type behaving as Epic.

So if you require a level above the current Epic and need that to be Epic, rename the Epic issue type/work item to lets say Feature and create a new issue type that you will call Epic.

In the Work Item section of Jira administration you will find the Work Item hierarchy, there you can place the new Epic above the renamed Epic, now Feature.

The Feature will have the ootb Epic functionality and the new Epic is just an work item like Story or Task

Akshay Mishra_4f5xm7

Thanks @Marc -Devoteam-

Just to summarize - if I understood your point correctly :

If "L" represents Level and my project is planned as " L1 --> L2 --> L3 --> L4 ",

Then L1 can be Features, L2 has to be epics, L3 has to be stories and L4 has to be tasks or sub-tasks - is it correct ?

So, I will interchange names for my epics and features.

Is my understanding correct ?

Marc -Devoteam-

HI @Akshay Mishra

If you want to retain the Epic functionality on L2, yes you can rename this to Feature and set L1 (new issue type or existing) rename this to Epic

Yes the L representation you are presenting is correct, this structure from L2 to L4 is set and can't be changed.

You can only add issue type on the same level or a higher level.

Joshua Brock _ Seibert Group_ GmbH

Greetings @Akshay Mishra

Looks like Marc offered you a great solution, staying within the functionality of Jira itself.

If down the road you're looking to fully implement SAFe®, while staying in Jira without any workarounds, I invite you to look at either our Cloud or DC version of Agile Hive. Our plugin is free if you're staying under the 10 user threshold in alignment with Atlassian.

We designed it from the ground up with assistance from KEGON, one of the leading SAFe® experts in Germany and the DACH region.

Our documentation here discusses configuring the hierarchy.

SaFe-Hierarchies (1).png

Best of luck and certainly if down the road you're looking for a integrated and extended solution, please reach out!

Joshua
Content & Technical Writer
Agile Hive

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

safe