SAFe Adoption / Changing Epics to Features

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. 

1 comment

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.

Comment

Log in or Sign up to comment
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,956 views 19 22
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you