SAFe® in Jira and Confluence
Jira is made for agile working and has taken up the appropriate values such as transparency, communication and collaboration. Thus, software development according to Scrum transparent communication within the team is enabled. This also creates a basis for SAFe, the Scaled Agile Framework for Lean Enterprises.
With these functions it is almost possible to realize an Essential SAFe® configuration for an ART. The flaws are the naming of the Jira epic, which cannot be renamed to feature, the lack of other issue types at the program level (e.g. enablers, risks, PI objectives), and the overall view of the PI is hard to get. There is no program board or other ways to clearly visualize dependencies.