The best solution for me would be to only update the Jira FixVersion if the following are both true:
- The Release has changed in Aha
- The FixVersion has not been edited in Jira
This would mean that I can change my plan in Aha as much as I want and the related Jira issues will be updated to match, until someone sets a specific FixVersion in Jira. At that point Aha would no longer update the FixVersion.
I realise that the second condition here may be very specific to my use case, but the first seems like it would be quite common.
Thank you for your idea. One suggestion that is now possible would be to set a links to mapping from the Aha! release to a custom field in Jira. For example, you could create an "Aha! release" field in Jira. Then when a feature is sent to Jira, the Aha! release will populate the custom field rather than the fix version field. Subsequent updates will then update the custom field, leaving the fix version field intact.
At this time, given the option above and historical support of this idea, we are unlikely to implement this idea. We hope you can understand.