You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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.