Jira & Aha Integration - Ability to refresh Aha records making either Jira or Aha the dominant source

What is the challenge?

We would like to have the ability to refresh the Aha record based on Jira updates. Currently, inside the integrated Aha ticket, users can only resend the updates they made in Aha into Jira, but not the other way around. We would like to have the ability to push data from Jira to Aha on a ticket level when necessary.

What is the impact?

Sometimes the integrated Jira ticket is updated but it takes time for the updates to flow into Aha. That creates data inconsistencies between the 2 systems. A workaround to fix this issue is to remove the integration and add it back, letting the Jira record to be the dominant one.

Describe your idea

Add an option to the integration field that allow users to decide if they want to have the Aha records refreshed with either Jira or Aha as the dominant data source.