@Diana Mourad,
Welcome to the Atlassian Community. I am a Solutions Architect with Cprime, an Atlassian Partner.
This is a particularly sticky question for Jira in that Epics are IssueTypes like other Jira Issue Types such as Story, Task, Bug, etc. A Jira Software Epic Issue Type is not a Sub-Task though. Epics have some characteristics that belong only to the Epic. Those are Epic Name, Epic Link, Epic Status, and Epic Color. You cannot simply rename the Epic to be a Solution Epic without breaking Jira. SAFe allows for Epics at a number of levels from Portfolio, Solution, and Program.
I have implemented SAFe in about a dozen Jira instances so the best way I found it to work is to use the Jira Epic as the Feature in SAFe. If you are using Atlassian Cloud your organization will have to do the mental Jira Epic = SAFe Feature as Atlassian Cloud will not allow you to rename the Epic and all 4 of its characteristics. If by chance you are on Data Center (DC) or Server you can get the Epic To Feature Translator from the Atlassian Marketplace to rename the Jira Epic to Feature. Otherwise, just create a new Issue Type (not sub-task type) call Solution Epic and use this in your SAFe Hierarchy. If you are using Portfolio you can use the Parent Link to link the Solution Epic to the correct Feature(s) at the Program level, which is now a part of Essential Level in SAFe v5.0.
Hopefully, this all makes sense?
Regards,
Bryan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.