Aha now honors additional Jira Types (other than just Stories and Features) - YAY! However, when the Jira Type is changed, it breaks the sync between the Jira item and Aha item.
Example: Support reports a "Support Defect", Dev reviews, changes it to a "Support Request" or even a "Story" if it is really more of an Enhancement request that came in. Or even an item starts as a Story and is promoted to a Feature.
Request: Please honor the changing Jira type on sync - even if this loses data from the original sync, keeping the item hooked to the Jira item is really important. I have lots of Aha 'orphans' that seem to be a result of the types changing in Jira.
|Release time frame
Aha! Roadmaps now honors changes to Jira issue type.
In order to maintain the bi-direction integration when an issue type is changed in Jira, your Jira integration settings within Aha! need to define a mapping for all of your Jira issue types. For example, you may have mappings for Feature -> User story, Feature -> Defect, and Feature -> Support escalation all defined within your Jira integration. Each of these mappings can contain different fields and behaviors, allowing you to share the most important information for each type of work.
Note that Aha! Roadmaps does not currently support changing the Aha! record type via an integration (i.e. changing an issue from a user story to an epic in Jira will not cause the feature in Aha! to be converted to an epic). This ensures you do not lose critical information in Aha! due to changes happening in Jira. If this functionality is important to you, please share details about your use case in https://big.ideas.aha.io/ideas/A-I-15789.