When an Aha! Release name is updated, it does not trigger an integration update for the associated Epics. As a result, the mapped release name field on Jira Epics becomes outdated and is only refreshed when each Epic is manually resent. In many cases, we only need to resend specific mapped fields rather than updating all field values. Therefore, using the update record function in the integration is not a suitable approach for our use case.
What is the impact?
This results in outdated or inconsistent information in Jira, increased manual effort for admins and product teams, and confusion for engineering teams who rely on Jira as their source of truth.
Describe your idea.
Updating an Aha! Release name does not trigger an integration update for Epics, causing Jira release fields to become outdated unless each Epic is manually resent, which does not scale.
