Requirements won't change Features when linked Jira issues are moved

The integration with Jira currently does not support making structural changes to requirements for issues that are moved in Jira. For example, assume a mapping where features = epics and requirements = user stories and existing links are in place. Moving a user story in Jira to a different epic will not move the requirement in Aha! to a different feature. The reverse is also true. Moving requirements to different features in Aha! will not update the corresponding Jira user story while it is still linked to another Jira issue. 

The process for handling these requirement parent item changes that typically will occur at the end of a release needs to be managed through Aha! using the following process:

  1. Click on the requirement and delete the link to the Jira issue by clicking on the trash can icon next to the integration link. 
  2. Click on the Actions menu for the requirement and select the Move to another feature option. Select the new parent feature you want to move the requirement to. If the feature that the requirement is moved to is already linked to a Jira epic, it will automatically create the new user story in Jira under the corresponding epic. 
  3. Delete the original orphaned user story in Jira that wasn't completed. 


Was this article helpful?
2 out of 3 found this helpful
Have more questions? Submit a request

Roadmap software to manage your products.
Finally, connect strategy to execution.

Powered by Zendesk