RELATED IDEAS
Support for an Aha! Initiative to create/map to Epics across multiple JIRA Projects
The use case is a requirement to have a single Aha! Initiative create/map to Epics that are in different JIRA Projects. Current support is that an Aha! Initiative can only be linked to a single JIRA Epic.
Simple example: Fredwin Cycling has an Epic called I18N. Fredwin Cycling is then mapped to a Frontend Project and Backend Project in JIRA. Aha! has Features for both the Frontend project and Backend project that are linked to I18N.
The requirement is that the I18N Epic will be created as an Epic for both the Frontend and Backend JIRA Projects and can support having features/user stories that are in different JIRA projects associated with that Epic.
© 2024 Aha! Labs Inc.•All rights reserved
Hi there. It is now possible to have an Aha! record (initiative, master feature, or feature) mapped to an epic in Jira, and then have child records mapped to records in other Jira projects. Scenario 2 in this article describes this in more detail. The article also includes details on how to set this up.
I am hoping to implement the following use case that is along the same concept as above:
1 Master Feature (mapped as epic in jira) is being linked to two Jira backlogs along with the child Features (mapped as stories in jira) that are broken down within it. When I try to get status in Aha, it does not show correctly.
Aha allows the integration to work with multiple jira backlogs but does not support duplicated epics/stories (especially status). There are also no checks and bounds in place to stop this from happening.
We map Aha! Features, not Initiatives, to JIRA Epics. Please make sure that this enhancement applies to both mappings: Aha! Initiatives/JIRA Epics and Aha! Features/JIRA Epics.