A question about ReflectedWorkItemIDFieldName

[code-on-git]

I'm not sure I have understood the whole purpose of ReflectedWorkItemIDFieldName.

I got it to work by using this setting on both source and target:
"ReflectedWorkItemIDFieldName": "Custom.ReflectedWorkItemId"
I also created a new field named "ReflectedWorkItemId" in each work item type in the processes that my source and target projects uses.
I also created a new group, called Migration, for the new field.

Is that what I'm supposed to do?

If so - I guess I'm not able to migrate a project that uses the built-in processes since you can't create custom fields in the built-in processes?

Am I missing something?
Can I use any of the existing fields for this purpose instead of creating a new?

[MrHinsh]

You can indeed use a built-in Field and If I were to choose I would use Microsoft.VSTS.Build.IntegrationBuild which is on every Work Item.

The danger of using a built in field is that its value can be changed outwith the tool by others or by Azure DevOps itself. This would break the ability for the migration to find the correct work item for Links.

You can add custom fields to an inherited process:

1. Create and manage inherited processes
2. Add and manage fields

[srousa]

I will check. but we just got the tool downloaded yesterday so I would assume the latest.

[MrHinsh]

Can you provide the log file?

[srousa]

thanks @MrHinsh we got it to work. Thanks !!
Small question - is it possible to disable preprocessing where it creates an Iteration and Area paths on the target? (we don't want to migrate an iteration path and for area path it ends up creating it at the wrong level and just adds a little mess).. thanks !

[MrHinsh]

We can't migrate work items without all the areas and Iterations existing. It's just how the system works.

You can however setup a mapping for any area or Iterations you want int a different place.

https://nkdagility.com/learn/azure-devops-migration-tools/Reference/v2/ProcessorEnrichers/TfsNodeStructure/

Use the following TfsNodeStructure:

 { 
"$type": "TfsNodeStructureOptions", 
"Enabled": true, 
"PrefixProjectToNodes": false, 
"NodeBasePaths": null, 
"AreaMaps": {}, 
"IterationMaps": {  }, 
"ShouldCreateMissingRevisionPaths": false, 
"ReplicateAllExistingNodes": false 
}

This will turn off the creator and tell you whats missing. Then add mapps that change the paths.

[srousa]

Thank you! That helped!