RELATED IDEAS
Integrate Master Features and related features to different JIRA projects
In this scenario, there is one Program product workspace in Aha! and one Program project in JIRA which contains Master Features per Agile Release Train. All Stories (Aha Features) and sub-tasks (Aha Requirements) are with one or many Agile Teams (Aha Products).
Master Features should be sent to the Program Level project within JIRA, instead of team boards. However, the Features related to the Master Feature need to be sent to different JIRA projects (team boards) based on the team working them.
© 2024 Aha! Labs Inc.•All rights reserved
This is a must for SAFe implementation.
In SAFe model Features (Aha Master Features) do not live in Team boards. All Features (Aha Master Features) goes to Program level Product. The setup should be one Program Product in Aha and one Program Project in Jira per Agile Release Train.
All Stories (Aha Features) and sub-tasks (Aha Requirements) can be with one or many Agile Teams (Aha Products).
Aha Master Features in Program Product should sync to Jira Program Project and rest of the Features from other Products should sync to respective Jira Projects maintaining Aha Master Feature > Feature > Requirement relationships.