How to synchronize existing Work Items on source and target without remap iteration/area

[dahikino]

i try to migrate some work items from a organisation project to another organision but i would like to synchronize in both sense to make
the work items up to date..

Creating the working items from org A to Org B is ok but how can i set the other config file for the other sense to synchronize org B to Org A but without to change the existing area or iteration path that are yet filled.

From Org A to org B i set a remap area / iteration but from Org B to Org A, the work items are yet always existing, i don't want to remap area or iteration !

[MrHinsh]

What you may be hitting is a moved work item or a deleted area/iteration path. If a Work iTem previously was set to this area/iteration and then subsequently the area/iteration was deleted, then it would not be valid to add this in the history. Area/iteration paths are the one thing that we cant bypass the rules for.

There are two options to resolve this:

Option 1: Add the missing area/iterations

This can be enabled automatically by using the ShouldCreateMissingRevisionPaths to true in the TfsNodeStructureOptions of the CommonEnrichersConfig list.

Option 2: Map the missing area/iterations

Add a field map to map the missing area/iterations (map the expected target area/iteration to an existing area/iteration). Then set StopMigrationOnMissingAreaIterationNodes to false to continue with the migration.