TfsWorkItemMigrationProcessor

[SinghGhanshyam]

This discussion is for questions, feedback, and community support related to the Tfs WorkItem Migration Processor.

Quick Reference

• Class Name: TfsWorkItemMigrationProcessor
• Friendly Name: Tfs Work Item Migration
• Documentation: Tfs WorkItem Migration Processor

How to Use This Discussion

• Ask Questions: If you need help configuring or using this component
• Share Examples: Post your configuration examples or use cases
• Report Issues: Describe any problems you encounter (though bugs should be reported as GitHub Issues)
• Request Features: Suggest improvements or new features

Related Documentation

Please refer to the official documentation for detailed configuration options and examples.

[MrHinsh]

What have you dont to resolve the error presented:

Unable to load Common Structure for Target.This is usually due to TFS having a different installed langauge version than was expected.. Validate that 'Area' is the correct name in your version. This would be something like 'Fläche' or 'Aire'. If you open the area tree in Visual Studio, or web access, you should see the name your langauage uses for 'Area' or 'Iteration. Do not try to add a specific area or iteration path to this field. Check the defaults on https://nkdagility.com/learn/azure-devops-migration-tools/Reference/Endpoints/TfsTeamProjectEndpoint/ for an example fro English.

[kai1512]

When migrating Workitems from a source Project other than the Project that holds the Repository for the added commits we get an error and the links to the commits don't work. Is there a way to fix this? The Repositories are all migrated already.

[DexLusterio]

Hello @MrHinsh . Is there a work item processor or a flag in it that migrates the changes made in field values? Last week we have made a work item migration and the team since then made work items comments as well as close the status in the source TFS. I like to make a run to update this in the already migrated work items in our ADO. Thanks

[MrHinsh]

No flag required. Thats how the tools work out of the box.

As long as there are revisions in the source with a more recent date to the target they will be migrated.