Given "Aha! is for the "why" and "what" and JIRA is for the "how."; Master Features are useless unless we can implement them alongside JIRA.
Once AHA Master Features = Epics in JIRA i'll be able to take full advantage of this feature!
I find it hard to believe that master features feature shipped without this integration being live
Please configure JIRA integration to allow mapping of Master Features across multiple Aha Products to a single Epic in JIRA.
We are currently in the process of setting up an integration between Aha! and Jira and would really need the Master Feature integration so that we do not need to change later. We are using "initiatives" as Epics today, but without Jira integration.
What is the ETA for delivery of this feature ? Linking Master feature to Epic instead of initiatives would be very useful, especially if the Epic can be created automatically in Jira from Aha!.
I agree - I don't think I can really use master features effectively until this feature has been implemented.
Please add support for this! I'm not able to use master features without this.
I don't want master features to be linked to Epics in Jira, because I already have Features linked as Epics. So when the integration is built, it must be configurable to not send master features as epics.
When Master Features group features, and features are Jira Epics, then the most important thing to get right is the update of the status of the master feature, according to the status of the features that is synced back from Jira. This behavior should be documented, and ideally configurable.
Looking forward to see Master Features being available for JIRA integration as Epics!
I agree with this request, but please keep in mind existing integrations. We're currently linking Aha! features to Jira epics, and Aha! requirements to Jira tasks. If that breaks, we're going to be in a world of trouble.
You won't be notified about changes to this idea.