Replies: 1 comment 1 reply
-
The 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/iterationsThis can be enabled automatically by using the Option 2: Map the missing area/iterationsAdd a field map to map the missing area/iterations (map the expected target area/iteration to an existing area/iteration). Then set |
Beta Was this translation helpful? Give feedback.
-
I'm having a bit of trouble understanding how to migrate Area Paths and Iterations into an empty project. I'm trying to move work items from a project in one organization into another in a different organization. These are both in ADO Services. The new project doesn't have any Area Paths or Iterations in it, but I have updated its process to support the ReflectedWorkItemId.
It seems like what previously was the NodeStructuresMigrationConfig processor has been deprecated and merged into the WorkItemMigration processor. How can I migrate the Area Paths using the WorkItemMigration process? How can I ensure this is run before the work items are migrated?
I am getting this error when trying to migrate:
This is potentially the same problem as #1452 (comment)
I have tried to set the PrefixProjectToNodes config to true vs false.
I cloned the repository yesterday.
What I have configured works if the Area Paths match between the projects.
Below is my configuration, any help would be appreciated!
Beta Was this translation helpful? Give feedback.
All reactions