CODEWITHSUNDEEP
custom-fieldsscrumazure-devops-migration-tools
Dick Wenning
Dick Wenning

Reputation: 1

work item migration, but custom fields where not available on the target environment

we started the worktime migration from DEVOP to other DEVOPS but we forget to create the board columns and a custom field Stakeholder (identity) So, we created and did run the migration tool again, but it did not set that stakeholder field. how can this be corrected? enter image description here also the assignment to the board column did not get corrected

we rerun it again, but it did not update those fields

Upvotes: 0

Views: 150

Answers (1)

MrHinsh - Martin Hinshelwood
MrHinsh - Martin Hinshelwood

Reputation: 23444

By default, any fields that exist with the same name on the Source will be automatically mapped to the Target. If there is a difference you will need to map the fields.

https://nkdagility.github.io/azure-devops-migration-tools/Reference/

Upvotes: 0

Related Questions