In Progress Migrated Work Items don't appear in Target Project Default board #3103
-
|
I have migrated all my work items from one Azure Devops Project into a new Azure Devops Project (in different Orgs). I have only migrated the Work Items, iteration and area paths. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
Spent a bit more time trying to work out what has happened. Should I have done some form of mapping between the source and target teams ?? |
Beta Was this translation helpful? Give feedback.
-
|
Looks like I have solved this problem. But, I solved it by cleaning my target project (removed all migrated work items, removed migrated team, removed migrated iterations and area paths). Then I changed the name of my source project to match the target project name (the Team name was also renamed). Now all the migrated work items are against the expected team, board and backlog in the target project. This process ay not work for everyone as I had a simple Source Project so renaming it wasn't a problem. |
Beta Was this translation helpful? Give feedback.
Looks like I have solved this problem.
My source and target projects were named differently and therefore the Teams were also named differently.
When I did the initial migration I did not do any custom mapping between Project or Team names.
I am not sure if I should have done or how I could do it.
But, I solved it by cleaning my target project (removed all migrated work items, removed migrated team, removed migrated iterations and area paths). Then I changed the name of my source project to match the target project name (the Team name was also renamed).
Then I did the Work Item migration again.
Now all the migrated work items are against the expected team, board and backlog in the target …