Move Aha! Requirements when linked JIRA Stories are Moved to a different Epic/Feature

The specific use case that this commonly occurs for is  the following mapping:

Feature = Epic and Requirement = Story; however, the same would apply to other mappings parent child mappings such as Story/Sub-task as well.  

Current behavior: The integration with JIRA currently does not support making structural changes to requirements in Aha! based on changes in JIRA. e.g. moving stories in JIRA will not move requirements in Aha!. Likewise, moving requirements to different features in Aha! will not make an update to the corresponding JIRA issue (i.e. Story) while it is still linked to another JIRA issue.

Desired behavior: If you a move a Story in JIRA that is linked to an Aha! Requirement to a different Epic (which is mapped to an Aha! Feature), the desired behavior is the Requirement would be moved from the original Aha! Feature to the new Aha! Feature.

The current process for handling this type of change:
1. Delete the link to the JIRA issue for the requirement (click on trash can next to link)
2. Use the Requirements Actions menu option to move the requirement using "Move to another feature". If the Feature it is moved to is already integrated with JIRA, it will automatically create the new story in JIRA under that Epic. 
3. You would then want to delete the original orphaned story in JIRA that wasn't completed.  

A more elegant solution for handling this is requested. 

  • Matt Case
  • Jun 3 2016
  • Likely to implement
Release time frame
  • Attach files
  • Tech Buff commented
    February 2, 2017 18:59

    Way too many steps to achieve this in the current Aha implementation, which really goes against the grain Aha's positioning as THE planning tool. Let's have this done :)

  • Phillip Jones commented
    February 14, 2017 23:53

    Is there any progress on getting this fixed.  My organization is using Aha as a Product Roadmapping tool, and our Roadmap is constantly drifting in terms of changes made in JIRA (specifically, User Stories moving between Epics).

  • Sam R commented
    February 15, 2017 09:51

    absolutely want to see this as our roadmap also drifts against jira and manual alignment negates the whole integration point....

  • Guest commented
    May 25, 2017 10:19

    The above three comments reflect my position too+++.  We also suffer from "roadmap drift" due to this problem - and it sometimes makes Aha! more of a hindrance than a help to us.

  • Guest commented
    May 25, 2017 10:29

    Just to add that I've added a new idea (https://big.ideas.aha.io/ideas/APP-I-4584) as a work-around to this problem, while we're waiting for this to be fixed.

  • Solveig Fiskaa commented
    August 22, 2017 05:32

    This error makes me loose confidence in AHA! as a planning tool and difficult to trust that AHA! reflects how the development goes along. Will always have to double check with Jira the status and amount of stories/bugs.

  • Leon Ward commented
    September 15, 2017 07:49

    It's VERY common to have stories moved between epics in our teams. This causes real pain with loosing track of things in Aha and having our board not represent engineering reality.

    I don't want to define how it should be fixed, perhaps the answer is better master feature -> epic sync, but it whatever the fix, it must prevent loosing the feature as it moves between epics that may or may not exist in Aha.