What happens for WorkIitem(s) that are copied from one project to another project #1625
-
|
The workitems which are copied from another projects. During those workitems are migration process, tool is expecting old project Areapath and Iteration paths are the at the root level. Areapath and Iteration path for rootpaths which ever project is doing migration. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
I'm not 100% sure that I understand your comment. When doing a migration, all of the Areas and Iterations that are anywhere in the history of a work item MUST exist in the target or be mapped to one that does. If a work item has been moved between projects then you need to add a mapping for the Areas and Iteration paths from the old project. All areas and iterations that do not exist will be listed in the logs, and by default the system will stop if they do not exist. |
Beta Was this translation helpful? Give feedback.
I'm not 100% sure that I understand your comment.
When doing a migration, all of the Areas and Iterations that are anywhere in the history of a work item MUST exist in the target or be mapped to one that does.
If a work item has been moved between projects then you need to add a mapping for the Areas and Iteration paths from the old project.
All areas and iterations that do not exist will be listed in the logs, and by default the system will stop if they do not exist.