Please add support for Master Features within the Aha <=> JIRA interface.

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.

  • Gravatar Guest
  • Mar 29 2017
  • Planned
  • Attach files
  • Michael Morrison commented
    March 29, 2017 18:36

    Once AHA Master Features = Epics in JIRA i'll be able to take full advantage of this feature!

  • Aaron Legge commented
    April 4, 2017 16:03

    I find it hard to believe that master features feature shipped without this integration being live

  • Simon Buchanan commented
    April 12, 2017 06:46

    Please configure JIRA integration to allow mapping of Master Features across multiple Aha Products to a single Epic in JIRA.

  • Kenneth Palm commented
    April 19, 2017 13:52

    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.

  • Etienne Poulin commented
    April 26, 2017 15:37

    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!.

  • Nick Kewney commented
    April 27, 2017 14:21

    I agree - I don't think I can really use master features effectively until this feature has been implemented.

  • Dan Diephouse commented
    May 2, 2017 21:10

    Please add support for this! I'm not able to use master features without this.

  • David Hegarty commented
    May 5, 2017 14:58

     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.

  • Casper Heintzelmann commented
    May 17, 2017 06:14

    Looking forward to see Master Features being available for JIRA integration as Epics! 

  • Patrick Matthews commented
    May 22, 2017 18:57

    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.

  • Paul Mundy commented
    June 2, 2017 16:29

    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

  • Ksawery Lisinski commented
    June 5, 2017 07:48

    When can we expect this integration to be shipped? 

  • Conner Helton commented
    June 6, 2017 17:20

    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!

  • Devik Lansing commented
    June 29, 2017 19:09

    I see this is marked "planned" This would have a huge benefit for us as well - is there a timeframe you can share?

  • Corina Toth commented
    July 6, 2017 14:59

    When can we expect this integration to be shipped? 

  • Guest commented
    July 19, 2017 07:48

    . If Carslberg made product management software they would have integrated and mapped master features to EPICS and called them EPICS. .

  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar