TFS4JIRA Cloud Native | How to update items after an initial synchronization.

Owned by Adriana Hernandez
Last updated: Apr 10, 2024
3 min read

After completing the initial synchronization, the items were successfully migrated. However, upon adding new mapping configurations and restarting the initial synchronization, the newly mapped fields do not appear on the previously migrated items.

 Workaround

Currently, TFS4JIRA Cloud Native only reviews items that have not been migrated or were recently updated. Therefore, when a new field is added to the field mapping, it must be triggered/updated in the source instance for TFS4JIRA Cloud Native to synchronize this new change during the next initial synchronization.

It is advisable to conduct the initial synchronization after mapping all the necessary fields and testing the migration in a test environment.

Sync profile - field mapping view

Nevertheless, if this issue occurs during the testing phase of the TFS4JIRA Cloud Native app, we suggest cloning the synchronization profile and initiating the initial synchronization from scratch or enabling the continuous synchronization and updating the item’s new field mapped on the source instance.

Steps to clone a sync profile

Let’s review the two recommended ways to retry an initial synchronization after new changes in the mapping:

Cloning the sync profile:

This option is recommended when the number of items migrated is too large.

  1. Delete all the migrated items from the target instance.

  2. Add the new mapping changes to the sync profile.

  3. Clone the sync profile.

    1.  

       

  4. Start the initial synchronization from the new sync profile.

    1.  

  5. The new fields will be synced by TFS4JIRA Cloud Native.

 

Updating the item in the source instance:

When the number of items migrated is manageable.

  1. Enable the continuous synchronization.

    1.  

       

       

  2. Add the new mapping changes to the sync profile.

    1.  

    2.  

       

  3. Trigger or update the new mapped fields directly on the source items. Re-entering the previous value or adding a dot will do. The source instance could be Jira or ADO but thill will depend on your sync direction.

    1.  

    2.  

  4. The new fields will be synced by TFS4JIRA Cloud Native.

It is important to NOT preforming any edit or create actions on items using the synchronizer user, TFS4JIRA Cloud Native skips changes made by the synchronizer user to avoid loops. For more details please see: https://appfire.atlassian.net/wiki/spaces/TFS4JIRA/pages/148177872.