What is the challenge? |
The release field is available in the Jira integration under the Aha! feature/epic record. It works as expected when initially sending the Aha! feature to Jira. (Note: this is not the use case of mapping the release as a separate record.) However, the mapped release field is not automatically updated in Jira when the text of the release name is changed in Aha! |
|---|---|
What is the impact? |
The use case is just changing the text of the existing release name, not changing which release is associated with the feature. Currently, need to manually select "Resend all fields" from each feature record in Aha! to update the release field in Jira. This would apply to any record where the release field can be mapped in the integration. |
Describe your idea |
When the release name is changed, trigger an integration update wherever the release name is mapped as a field on other records. |