We currently use the default setup in JIRA where Epics are linked to Initiatives and Stories are linked to Features in Aha. We have a fairly complex release planning process where JIRA versions and Aha 'Releases' do not match up at all. This is because we release code every sprint, but need to schedule major releases with full company involvement.
These major releases would be a great place to leverage Aha to do capacity planning, schedule phases, etc. Except Aha doesn't really operationally integrate well enough to enable it. We'd like to have all tasks, stories, etc created and linked to the epics in JIRA that are planned to release to sync with Aha and enable us to show progress toward the major release. Unfortunately, in Aha, features can only manually be added to release or synced through the JIRA version number.
This doesn't really work given our setup.
Enable syncing releases to initiatives rather than features. Automatically sync all features from associated initiatives to releases.
It seems like all the features around releases are built toward long-term release planning. They generally contain multiple initiatives and multiple phases. However, currently in order to add features to releases the have to be either added manually in Aha or synced to version number in JIRA. Since each release our team is releasing hundreds of individual features it is unmanageable to manually sync this. In addition, as new tasks and features are added in JIRA, these things do not sync to the release, making all the tracking and planning available in releases irrelevant.
We currently get around this by not using releases at all and having a report around the specific epics / initiatives we want to release. However, we could use releases if this change were made.
|Release time frame|
Thank you for your idea and for providing such thoughtful detail. We are not planning to make changes in this area at this time since initiatives are likely to span multiple releases.
Regarding the challenges you are facing with the JIRA integration, as you think about the integration between Aha! and JIRA, it is important to understand that Aha! helps you manage the why (Strategy), the when (Releases), and the what (Features). Where JIRA helps you manage the how. As such, the integration is designed for Aha! to come first in the process. You can read more about this here: https://support.aha.io/hc/en-us/articles/202001127-How-to-think-about-integrating-Aha-and-JIRA-two-way-
In this way, after you've planned your releases in Aha! you can push the features and initiatives to JIRA and everything will automatically sync. If you already have features in JIRA, you can also do an import into releases to prevent any manual input: https://support.aha.io/hc/en-us/articles/202000917-Import-features-from-Jira