How-To: User Mappings

[MrHinsh]

This discussion is for questions, feedback, and community support related to the How-To: User Mappings.

Quick Reference

• Documentation: How-To: User Mappings

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.

[ValerianHs]

Hi,
do you have an updated how-to for v16.x?
Thankfully

[MrHinsh]

This should be updated in preview with #2858, can you check and see whats what? Give it 5m to get from dev to preview.

[MrHinsh]

https://blue-river-093197403-preview.westeurope.5.azurestaticapps.net/docs/how-to/user-mappings/

[veinito]

Hey Hi,

I'd appreciate any help from your side Guys, as I've already spent half a day on it and still no luck.
Shall I report it in a different way or elsewhere - let me know.

So, trying to run TfsWorkItemMigrationProcessor and TfsUserMappingTool with manually prepared user map .json file (as export failed with same error message given below).

This is my config file:

{
  "$schema": "https://devopsmigration.io/schema/configuration.schema.json",
  "Serilog": {
    "MinimumLevel": "Information"
  },
  "MigrationTools": {
    "Version": "16.2",
    "Endpoints": {
      "Source": {
        "EndpointType": "TfsTeamProjectEndpoint",
        "Collection": "https://dev.azure.com/XXX/",
        "Project": "AAA",
        "Authentication": {
          "AuthenticationMode": "AccessToken",
          "AccessToken": "token"
        },
        "ReflectedWorkItemIdField": "Custom.ReflectedWorkItemId",
        "LanguageMaps": {
          "AreaPath": "Area",
          "IterationPath": "Iteration"
        }
      },
      "Target": {
        "EndpointType": "TfsTeamProjectEndpoint",
        "Collection": "https://dev.azure.com/YYY/",
        "Project": "BBB",
        "Authentication": {
          "AccessToken": "token"
        },
        "ReflectedWorkItemIdField": "Custom.ReflectedWorkItemId",
        "LanguageMaps": {
          "AreaPath": "Area",
          "IterationPath": "Iteration"
        }
      }
    },   
    "CommonTools": {
      "TfsUserMappingTool": {
        "Enabled": true,
        "UserMappingFile": "C:\\projects\\ADO\\user_mappings.json",
        "MatchUsersByEmail": false,
        "IdentityFieldsToCheck": [
          "System.AssignedTo"
          "System.ChangedBy",
          "System.CreatedBy",
          "Microsoft.VSTS.Common.ActivatedBy",
          "Microsoft.VSTS.Common.ResolvedBy",
          "Microsoft.VSTS.Common.ClosedBy"
        ]
      }
    },
    "Processors": [
      {
        "ProcessorType": "TfsWorkItemMigrationProcessor",
        "Enabled": true,
        "UpdateCreatedDate": true,
        "UpdateCreatedBy": true,
        "WIQLQuery": "SELECT [System.Id] FROM WorkItems WHERE [System.TeamProject] = @TeamProject AND [System.ChangedDate] > @today - 8 AND [System.WorkItemType] IN ('Epic') ORDER BY [System.ChangedDate] desc",
        "FixHtmlAttachmentLinks": true,
        "WorkItemCreateRetryLimit": 5,
        "FilterWorkItemsThatAlreadyExistInTarget": true,
        "GenerateMigrationComment": true,
        "SourceName": "Source",
        "TargetName": "Target"
      }
    ]
  }
}

Execution log:

[10:54:00 INF] [16.2.9] Validating::Check that all work item types needed in the Target exist or are mapped 
[10:54:00 INF] [16.2.9] Validating::Check all Target Work Items have the RefectedWorkItemId field 
[10:54:00 INF] [16.2.9] Validating::Check that all Area & Iteration paths from Source have a valid mapping on Target 
[10:54:01 INF] [16.2.9] Validating::Check that all users in the source exist in the target or are mapped! 
[10:54:01 INF] [16.2.9] TfsUserMappingTool::GetUsersInSourceMappedToTarget Loading identities from source server 
[10:54:01 INF] [16.2.9] TfsUserMappingTool::GetUsersListFromServer Found 881 identities (users and groups) in server. 
Error logged to Elmah.io! 
!! Check for latest version - We fix issues constantly - If not, please create a discussion on https://github.com/nkdAgility/azure-devops-migration-tools/discussions so we can get this fixed !!
[10:54:28 WRN] [16.2.9] TfsUserMappingTool::GetUsersListFromServer::[user:S-1-9-1551374245-1204400969-2402986413-2179408616-3-1799548171-706465091-2640529154-3530057890] Failed With Server was unable to process request. ---> There was an error generating the XML document. ---> Instance validation error: '5' is not a valid value for Microsoft.TeamFoundation.Framework.Server.ApplicationGroupSpecialType. 

(...)
50 times above error
(...)

[11:16:40 INF] [16.2.9] TfsUserMappingTool::GetUsersListFromServer 5086 user identities are applicable for mapping 
[11:16:40 FTL] [16.2.9] Error while running TfsWorkItemMigrationProcessor 
System.InvalidOperationException: Sequence contains more than one matching element
   at System.Linq.Enumerable.SingleOrDefault[TSource](IEnumerable`1 source, Func`2 predicate)
   at MigrationTools.Tools.TfsUserMappingTool.GetUsersInSourceMappedToTarget(TfsProcessor processor) in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Tools\TfsUserMappingTool.cs:line 193
   at MigrationTools.Tools.TfsUserMappingTool.GetUsersInSourceMappedToTargetForWorkItems(TfsProcessor processor, List`1 sourceWorkItems) in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Tools\TfsUserMappingTool.cs:line 217
   at MigrationTools.Processors.TfsWorkItemMigrationProcessor.ValidateAllUsersExistOrAreMapped(List`1 sourceWorkItems) in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Processors\TfsWorkItemMigrationProcessor.cs:line 256
   at MigrationTools.Processors.TfsWorkItemMigrationProcessor.InternalExecute() in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Processors\TfsWorkItemMigrationProcessor.cs:line 147
   at MigrationTools.Processors.Infrastructure.Processor.Execute() in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools\Processors\Infrastructure\Processor.cs:line 99
Error logged to Elmah.io! 
!! Check for latest version - We fix issues constantly - If not, please create a discussion on https://github.com/nkdAgility/azure-devops-migration-tools/discussions so we can get this fixed !!
[11:16:40 INF] [16.2.9] TfsWorkItemMigrationProcessor completed in 00:00:00  
[11:16:40 ERR] [16.2.9] TfsWorkItemMigrationProcessor The Processor MigrationEngine entered the failed state...stopping run 
[11:16:40 INF] [16.2.9] Command ExecuteMigrationCommand completed in 00:24:48.7267934

System.Linq.Enumerable.SingleOrDefault throws that Exception.

Cheers
Tomek

[MrHinsh]

Its finding more than one entry that matches... so it throws on that. This prevents invalid data.

What versions are you using? TFS/Azure DevOps Server? Azure DevOps Service?

5086 is a lot of identieis...

[veinito]

it's Azure DevOps Service

Its finding more than one entry that matches..

that matches email or name? Can you point me in a good direction?

Another thing is that I've prepared the .json file on my own (format taken from: https://devopsmigration.io/docs/how-to/user-mappings/) which I failed generating automatically via your tool (for the very same reason: SingleOrDefault exception), to bypass this issue. And I'm wondering why the migration tool is checking on all 5k+ identities, while it shall only read the map from the .json file. My understanding after reading https://devopsmigration.io/docs/how-to/user-mappings was that the typical procedure goes like this:

1. export users to .json file via TfsUserMappingTool and TfsExportUsersForMappingProcessor
2. manipulate that .json file manually to address all users names mismatches etc.
3. run TfsWorkItemMigrationProcessor with TfsUserMappingTool but this time no export shall happen, only mapping users from .json map + adding new work items
   that was my assumption and I wonder if that's correct - is it?