-
|
it happen that some people remove iterations and the synchro stop to work for these work items mentionning in their revisions the iteration ! |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
|
Please read the error message for missing iterations carefully and follow the provided instructions. Aditional info; #1846 |
Beta Was this translation helpful? Give feedback.
-
|
My problem comes from the fact some iterations have been removed from the target and second pass of sync process find some tickets with revisions mentioning these iterations. |
Beta Was this translation helpful? Give feedback.
-
|
Please read the error message for missing iterations carefully and follow the provided instructions. Aditional info; #1846 |
Beta Was this translation helpful? Give feedback.
-
|
As per the documentation, you need to add Iteration Maps and Area Maps that adapt the old locations to new ones that are valid in the Target. Before your migration starts it will validate that all of the Areas and Iterations from the Source work items revisions exist on the Target. Any that do not exist will be flagged in the logs and if you have "StopMigrationOnMissingAreaIterationNodes": true, set the migration will stop just after it outputs a list of the missing nodes. Our algorithm that converts the Source nodes to Target nodes processes the mappings at that time. This means that any valid mapped nodes will never be caught by the This path is not anchored in the source project message as they are already altered to be valid. We recently updated the logging for this part of the system to more easily debug both your mappings and to see what they system is doing with the nodes and their current state. You can set "LogLevel": "Debug" to see the details. To add a mapping, you can follow the documentation |
Beta Was this translation helpful? Give feedback.
As per the documentation, you need to add Iteration Maps and Area Maps that adapt the old locations to new ones that are valid in the Target.
Before your migration starts it will validate that all of the Areas and Iterations from the Source work items revisions exist on the Target. Any that do not exist will be flagged in the logs and if you have "StopMigrationOnMissingAreaIterationNodes": true, set the migration will stop just after it outputs a list of the missing nodes.
Our algorithm that converts the Source nodes to Target nodes processes the mappings at that time. This means that any valid mapped nodes will never be caught by the This path is not anchored in the source project messag…