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.
I agree with original poster and Michael Morrison's comment, I've been racking my brains trying to work with Initiatives and Features, and adding Master Feature is a perfect solution for Aha, but with no JIRA integration it renders the whole thing utterly pointless.
I get it that we're all iterative and agile and not everyone integrates with JIRA but this was an oversight to not at least immediately produce a planned release date for the integration. It only needs to be a tick box and a drop down. Link EPIC to Initiative or Master Feature. Real simple but resolves a massive headache.
Thanks in advance
When can we expect this integration to be shipped?
Agree with all comments here, we have engineers who track major features in JIRA as epics so that each task, requirement, improvement, etc are all associated and grouped nicely. This would be HUGE, I'd +5 vote this if I could!
I see this is marked "planned" This would have a huge benefit for us as well - is there a timeframe you can share?
. If Carslberg made product management software they would have integrated and mapped master features to EPICS and called them EPICS. .
Is there a short term work around for this? Any way to link an aha master feature to an issue as if it were a feature?
I'd like to ask the same question, any news/update on the planned timeline for this one? Next week looks good!
This is pretty urgent for us. Having just set up all the master features as epics in AHA then manually created these epics in JIRA and then manually sorted them all only to watch them all happily re-map back to the original two initiatives at the first sync. . And now, of course, all the dev see presented in the JIRA backlog is everything mapped to one of two EPICS (initiatives) which makes it very difficult to work with as there are no longer that nice level of granularity to group the user stories in understandable chunks of work. Sigh.......... Just seems to be a lot of duplication with AHA at the moment rather than a nice helpful seamless workflow between the two. Doesn't feel to me as if the ideas portal is very effective as the new stuff getting drip fed out doesn't seem to match the user voting?
We are getting close to release on the ability to map JIRA Epics to Master features. It is part of a major rework of how integrations operate that we have been working on for quite a few months.
The votes in the ideas portal make a difference for features that get shipped - have a look at the popular ideas which have already shipped - it is just that the most popular features also tend to be some of the largest, so they take time to implement :-)
Aha - Can you advise when this is likely to be released please?
I hope this will help resolve our integration issues. Mapping Jira epics to initiatives just doesn't work that well. They never show any level of completion based on work done in Jira, and they mostly just sit there not taking advantage of what initiatives are meant to be for in Aha. But the most frustrating thing is that because the integration is entirely keyed on the Initiatives, our Jira epics that span multiple releases constantly have their features remapped to whatever fix version the initiative got associated with first. Will master features be able to span multiple releases? If a team splits a story into two in Jira, I can't have Aha moving it to a different release.
You won't be notified about changes to this idea.