How do i handle migrating Test Plans and Suites with assigned users that are gone?

[MerrickGhali]

Hello, running into an issue where I keep getting this error
"The identity value '{Redacted User Name}' for field 'Assigned To' is an unknown identity." because that user has left our company and is no longer in active directory. Same exact error message you would get if you tried to create any kind of work item in the UI and assign someone not present.

What I find odd is this works for me and successfully assigned that user that's gone when i ran TfsWorkItemMigrationProcessor for any work items they were assigned to.

This wouldn't be an issue if I could get the user mapping to work but when exporting users it either filters down to zero or today i started getting this error:

[16:12:02 FTL] [16.0.9] Error while running TfsExportUsersForMappingProcessor System.InvalidOperationException: Sequence contains more than one matching element at System.Linq.Enumerable.SingleOrDefault[TSource](IEnumerable1 source, Func2 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 177 at MigrationTools.Tools.TfsUserMappingTool.GetUsersInSourceMappedToTargetForWorkItems(TfsProcessor processor, List1 sourceWorkItems) in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Tools\TfsUserMappingTool.cs:line 201
at MigrationTools.Processors.TfsExportUsersForMappingProcessor.InternalExecute() in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Processors\TfsExportUsersForMappingProcessor.cs:line 55
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 !!`

Any help or advice is appreciated.

[MrHinsh]

You can assign all Test Plans and Suits that are currently assigned to users that have left to users that you still there in the Source project?

[MerrickGhali]

Are you suggesting that I just write a script to go figure out if a test plan or suite still has a valid user and if not assign a default user? I suppose i could do that, just trying to figure out why work items works to set the old invalid user. I tried looking to see if i could force it to accept an invalid user as well in the Test plan template but that didn't work.

We have a pretty old tool that does migrations for us i was trying to replace with this because it's pretty old and never been updated and the original author is gone. It sets a default user in these cases for test plans and suites. I was thinking about trying to look at how that one handled it. Maybe an update could be made to this tool to do the same if it's possible. Might be helpful to others :)