custom team members are not migrating when using TfsUserMappingTool

[Lokeshmaxi]

custom team members are not migrating when using TfsUserMappingTool

Version:16.1.0

Requirement: expecting to migrate members in the custom team also to migrate towards target project,as gone through documentation ,discussions, i have followed steps and configuration , attaching below for better visibility

Step 1: export all users from source organisation

"Processors": [
{
"ProcessorType": "TfsExportUsersForMappingProcessor",
"Enabled": true,
"WIQLQuery": null,
"OnlyListUsersInWorkItems": false,
"ExportAllUsers": true,
"UserExportFile": "D:\devops\New folder\azuremigration\new\user-newmapping.json",
"SourceName": "Source",
"TargetName": "Target"
}
],
"CommonTools": {
"TfsUserMappingTool": {
"Enabled": true,
"UserMappingFile": "D:\devops\New folder\azuremigration\new\user-newmapping.json",
"MatchUsersByEmail": true,
"IdentityFieldsToCheck": [
"System.AssignedTo",
"System.ChangedBy",
"System.CreatedBy",
"Microsoft.VSTS.Common.ActivatedBy",
"Microsoft.VSTS.Common.ResolvedBy",
"Microsoft.VSTS.Common.ClosedBy"
]
}
}
}
}

Step 2: created user-mapping.json

tested in two types of format separately

a) [
{
"Source": {
"FriendlyName": "user_20",
"AccountName": "user@gmail.com"
},
"target": {
"FriendlyName": "user_20",
"AccountName": "user@gmail.com"
}
}
]

b){
"user@gmail.com": "user@gmail.com"
}

note: please confirm whether above two formats are correct,if wrong,please share correct one.

Step 3: Added TfsTeamSettingProcessor with workitemmigrationprocessor for usermapping & enrichers

{
"ProcessorType": "TfsTeamSettingsProcessor",
"Enabled": true,
"MigrateTeamSettings": true,
"UpdateTeamSettings": false,
"PrefixProjectToNodes": false,
"MigrateTeamCapacities": true,
"Teams": null,
"UseUserMapping": false,
"SourceName": "teamSource",
"TargetName": "teamTarget"
},
{
"ProcessorType": "TfsWorkItemMigrationProcessorOptions",
"Enabled": false,
"ReplayRevisions": true,
"PrefixProjectToNodes": false,
"UpdateCreatedDate": true,
"UpdateCreatedBy": true,
"WIQLQueryBit": "AND [System.WorkItemType] NOT IN ('Test Suite', 'Test Plan','Shared Steps','Shared Parameter','Feedback Request')",
"WIQLOrderBit": "[System.ChangedDate] desc",
"LinkMigration": true,
"AttachmentMigration": true,
"AttachmentWorkingPath": "c:\temp\WorkItemAttachmentWorkingFolder\",
"FixHtmlAttachmentLinks": false,
"SkipToFinalRevisedWorkItemType": false,
"WorkItemCreateRetryLimit": 5,
"FilterWorkItemsThatAlreadyExistInTarget": false,
"PauseAfterEachWorkItem": false,
"AttachmentMaxSize": 480000000,
"AttachRevisionHistory": false,
"LinkMigrationSaveEachAsAdded": false,
"GenerateMigrationComment": false,
"WorkItemIDs": null,
"MaxRevisions": 0,
"UseCommonNodeStructureEnricherConfig": false,
"NodeBasePaths": null,
"AreaMaps": {},
"IterationMaps": {},
"MaxGracefulFailures": 0,
"SkipRevisionWithInvalidIterationPath": false,
"SkipRevisionWithInvalidAreaPath": false,
"ShouldCreateMissingRevisionPaths": true,
"UserMappingFile": "D:\devops\user-mapping.json",
"Enrichers": [
"TfsUserMappingEnricher"
]
}

Expectation: what am expecting is whether members in the teams from source project can be migrated to target project is possible or not? if yes, please help on Detailed steps in Sequential order, also share example configuration , and also confirm whether different mail id users is supported eg: (source have user@abc.com,target have user@xyz.com with same displayname). i would appreciate,if you add real time examples for each processor and tools for all edge cases in both github and youtube for references.Thanks in Adavance

[MrHinsh]

The purpose of TfsUserMappingTool is to map users that exist in the source to other users that exist in the target.

At no time do we add any users to the target or mess with Entra ID in any way. All users for mapping must already exist. Any users that are the same between source and destination are mapped automatially.

[nee-k-hashedin]

1. What you mean by same user? User with the exact same names or same accounts (emails), which would be migrated automatically?

[MrHinsh]

Yes.

Note: yoru config is totally invalid. Run it through devopsmigration update to clean it of invalid stuff...