Two-way integrations between Aha! and development systems allow teams to keep large amounts of data in sync as changes occur in real time. However, there are instances where a customer may need to trigger a manual update from their development system — the Update records option allows just that.
Click any of the following links to skip ahead:
Why is it necessary?
It's helpful to understand why this might be necessary so you can implement safeguards as appropriate. We have seen two key events:
- New field mappings are added, resulting in all currently linked items having that field out of sync.
- A misconfiguration occurs, such as a user accidentally removing or disabling their webhook within Jira.
In either of these situations, the Update records option allows Aha! customers to easily use the data in Jira to update Aha! and get the two systems back in sync with each other.
How it works
This action is located within your Workspace settings, so you will need to have workspace owner access to the product in which you wish to run the Update records action.
Simply navigate to Settings ⚙️ > Workspace and click the integration you want to update on the left navigation. The first page that loads will have the Update records option on the bottom right. Click Update records to initiate a re-sync of all integrated records for the specific integration from the development system to Aha!
It is important to understand that this action will only update existing integrated records from your development system to Aha! It will not import new records that may exist. It will, however, send an update to the development system for any one-way mapped fields.
If you wish to import new records from your development system, you will need to use the Import records option located at the bottom of the page. To force an update of data from Aha! to your development system, the best choice is to use the Resend all fields option on an Aha! release. This will trigger the re-sync of the release as well as all epics, features, and requirements within the release.