Resync and Hard Resync
PreviousCorrect Usage of the Resolution Field in Jira IntegrationNextSynchronizing Existing Items on Both Sides
Last updated
Last updated
Sometimes overlooked, Resync and Hard Resync are great options to prompt Getint to sync your tasks again. If you’ve made changes to your integration and want to sync your issues without updating them manually within each app, the resync options are your best bet, depending on your recent modifications.
Resync/Hard Resync will always put an item for the earliest integration execution and process it.
Resync:
Resync refers to marking an item for resynchronization. When synchronization is executed, Getint compares the item data fetched from the app with the internal database field data and syncs only those that have changed.
In the context of Getint, Resync typically involves updating specific fields (such as Assignee, Status, and/or Description, to name a few) for synced items.
For example, it can be useful when changes occur in the source system (i.e., an issue’s status changes in Jira), and you want those updates reflected in Getint, but the issue failed to sync during the first run.
Hard Resync:
A Hard resync is a more comprehensive synchronization process as it involves re-evaluating all data and applying any necessary updates, even if there haven’t been explicit changes.
Hard resyncs will mark an item for resynchronization, when sync is executed, Getint treats all fields as modified which forces their resync.
Comments & Attachments - only those that were not yet synced in both cases will be synchronized.
Open your integration and go to Latest synced items.
Locate the item you want to resync and click the 3-dot button on the right.
Select Resync or Hard Resync depending on the changes made to the task, and wait for the integration to trigger a synchronization run. If you applied the necessary changes to either the integration or the app that was causing the failed sync, the item should now properly sync.
Initially, the sync failed due to an inappropriate mapping for statuses. However, after addressing this issue and initiating a resync, the task now transfers correctly to the other side, as evident in the image above.
To ensure proper synchronization when using this feature, it’s crucial to make adjustments to your integration and instances based on the errors encountered.
