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.
|Release time frame|