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

SAFe Adoption / Changing Epics to Features

Parag Matalia

We are in the midst of a SAFe transformation and would like to start using Jira and Jira Portfolio as part of this effort. We noticed that when trying to configure issue types in Jira, the Epic issue type can not be relabeled/renamed to Feature to adhere to SAFe. Ultimately, we are looking to use the following requirements hierarchy/linkage for our SAFe Portfolio Configuration:

Portfolio Epic <-- Program Epic <-- Feature <-- User Story

Has anyone been successful at configuring Jira to accommodate the aforementioned requirements hierarchy that is specific to SAFe?

Thank you in advance for any assistance/help.

Comments

Kat Warner

Not sure if this is still an ongoing question for you @Parag Matalia. If it is, check out Scaled Agile Framework (SAFE) and check out the LinkedIn group mentioned. that will be my next step.