Status Future consideration
Categories Jira
Created by Matt Case
Created on Jun 3, 2016

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. 

  • Attach files
  • Daniel Pokrývka
    Feb 24, 2020

    UPDATE: this seems working already in AHA/JIRA. 

    Only exception is when you move story to a different JIRA project and/or link to epic in different JIRA project.

  • Daniel Pokrývka
    Nov 5, 2019

    UPDATE:

    Epic link update on story level in JIRA solved by Attlasian - event gets fired properly. See versions and details (both server and cloud version): 

    https://jira.atlassian.com/browse/JSWSERVER-12299
    https://jira.atlassian.com/browse/JSWSERVER-11149
    https://jira.atlassian.com/browse/JSWCLOUD-15973

  • Daniel Pokrývka
    Sep 12, 2019

    just adding more pain here: we are moving component teams into one platform team .. and restructuring epics and stories ..(features and requirements linked to JIRA epics and stories), and because stories have already been linked with epics, aha can not pull them up to new epics..  this problem causes so much friction between an honest aha evangelist (me) and the rest of the company.....

  • Daniel Pokrývka
    Aug 27, 2019

    I have submitted an idea for "quick fix" on epic (feature) level in AHA - "make epic great again" button: https://big.ideas.aha.io/ideas/A-I-8138

  • Daniel Pokrývka
    Aug 27, 2019

    I have this pain with moving stories in JIRA and invalid mappings in AHA too. Just a hint to the current process description - I have found out that Step nr. 2 (move function of requirement in aha) actually triggers the change into JIRA too (only when within boundaries of the same integration 2.0 to JIRA (meaning in the same JIRA project).

  • Nerissa Muijs
    Jun 6, 2019

    This is especially painful when shipping releases - jira stories are moved out to new epics, yet the link isn't updated.

    We're about to change our release cycle process and this lack of functionality is going to cause my team and I considerable pain.

    Any news on when this will be implemented?

  • Leon Ward
    Sep 15, 2017

    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.

  • Solveig Fiskaa
    Aug 22, 2017

    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.

  • Guest
    May 25, 2017

    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.

  • Guest
    May 25, 2017

    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.

  • Sam R
    Feb 15, 2017

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

  • Phillip Jones
    Feb 14, 2017

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

  • Tech Buff
    Feb 2, 2017

    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 :)