Replies: 3 comments
-
I got some errors from the logs: |
Beta Was this translation helpful? Give feedback.
-
@cepcruzz links will be skipped for for work items that don't exist yet. If you are Migrating WorkItemA and WorkItemB which are linked then when the first one is created it cant yet create the link as the other does not yet exist. |
Beta Was this translation helpful? Give feedback.
-
Hi @MrHinsh appreciate the response. I got it! Thanks, apparently the issue was my query. I understand now. The migration tool found out that the work item has links but the linked work item was not included on my query. Hence was not migrated.. Any, thats for the basic work items like epic, feature, tasks. But how about the the items like Code Review and Shared Steps? How can we migrate it if we cant add custom fields on those kinds of items? :) |
Beta Was this translation helpful? Give feedback.
-
This is for issues: For questions on usage please use https://stackoverflow.com/questions/tagged/azure-devops-migration-tools and tag with
azure-devops-migration-tools
Describe your issue:
Migrating workitems, i was able to migrate the workitems like Epic, Feature, Task, and Requirement. But the relationships are missing. The feature that was link to the Epic from the source organization is now linked in the target organization.
Please try to describe your objective.
Describe any Exceptions:
Heres the snippet of the processor WorkItemMigrationConfig
Source Details
Target Details
I have completed the following:
"LogLevel": "Debug"
in the configuration file which will output more information to the log.Many issues are due to edge cases and will need debugging in Visual Studio; we cant do that for you on your environment.
Beta Was this translation helpful? Give feedback.
All reactions