Test Cases are getting blank Shared Parameters

[flavs97]

I am migrating from TFS to Azure, and some Test Cases have blank Shared Parameters, even though the Shared Steps have been created successfully. The execution log only shows this error, but I don't know if it would be enough to cause this problem in the Test Cases.

{"Timestamp":"2024-09-18T18:05:56.5065167-03:00","Level":"Error","MessageTemplate":"Microsoft.TeamFoundation.WorkItemTracking.Client.FieldDefinitionNotExistException: TF26027: uma definição de campo Microsoft.VSTS.Common.ClosedDate no arquivo de definição de tipo de item de trabalho não existe. Adicione uma definição para esse campo ou remova a referência ao campo e tente novamente.\r\n em Microsoft.TeamFoundation.WorkItemTracking.Client.FieldDefinitionCollection.get_Item(String name)\r\n em Microsoft.TeamFoundation.WorkItemTracking.Client.FieldCollection.get_Item(String name)\r\n em MigrationTools.Processors.TfsWorkItemMigrationProcessor.PopulateWorkItem(WorkItemData oldWorkItemData, WorkItemData newWorkItemData, String destType) na D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Processors\TfsWorkItemMigrationProcessor.cs:linha 422\r\n em MigrationTools.Processors.TfsWorkItemMigrationProcessor.ReplayRevisions(List`1 revisionsToMigrate, WorkItemData sourceWorkItem, WorkItemData targetWorkItem) na D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Processors\TfsWorkItemMigrationProcessor.cs:linha 768","TraceId":"ea083e8e4f872b29fd4e29113d800012","SpanId":"c2d9eb65aede96f7","Properties":{"SourceContext":"MigrationTools.Processors.TfsWorkItemMigrationProcessor","versionString":"16.0.3","targetWorkItemId":null,"sourceRevisionInt":4,"sourceWorkItemId":68004,"totalWorkItems":2853,"currentWorkItem":2566,"sourceWorkItemTypeName":"Shared Parameter","ProcessId":6724}}

My configuration.json

{
"MigrationTools": {
"Version": "16.0",
"Endpoints": {
"Source": {
"EndpointType": "TfsTeamProjectEndpoint",
"Collection": "---",
"Project": "---",
"Authentication": {
"AuthenticationMode": "AccessToken",
"AccessToken": "---"
},
"ReflectedWorkItemIdField": "System.ReflectedWorkItemId"
},
"Target": {
"EndpointType": "TfsTeamProjectEndpoint",
"Collection": "---",
"Project": "---",
"Authentication": {
"AuthenticationMode": "AccessToken",
"AccessToken": "---"
},
"ReflectedWorkItemIdField": "Microsoft.VSTS.Build.IntegrationBuild"
}
},
"Processors": [
{
"ProcessorType": "TfsWorkItemMigrationProcessor",
"Enabled": true,
"WIQLQuery": "SELECT [System.Id] FROM WorkItems WHERE [System.TeamProject] = @teamproject AND [System.WorkItemType] IN ('Test Case','Shared Steps','Shared Parameter') AND [System.Title] NOT CONTAINS 'REUTILIZAR' AND [System.Title] NOT CONTAINS 'Reginaldo' AND [System.Title] NOT CONTAINS 'Scenario Outline' AND [System.Title] NOT CONTAINS 'Esquema do Cenário' AND [System.Title] NOT CONTAINS 'Cenrio' AND [System.Title] NOT CONTAINS 'Cenrio:' AND [System.Title] NOT CONTAINS 'Cenário:' ORDER BY [System.ChangedDate] desc",
"LinkMigration": true,
"NodeStructureMigration": true,
"FieldMaps": [
{
"ObjectType": "FieldToFieldMapConfig",
"WorkItemTypeName": "*",
"SourceField": "Microsoft.VSTS.TCM.Steps",
"TargetField": "Microsoft.VSTS.TCM.Steps"
}
],
"WorkItemCreateRetryLimit": 5,
"AttachmentMigration": true
}
]
}
}

Here is the log, I followed theHow-to: Migrating Plans and Suits steps, I am running the second step to migrate TestCases and Shared Steps

migration.log

[MrHinsh]

You cant migrate work items that dont have Microsoft.VSTS.Common.ClosedDate with the TfsWorkItemMigrationProcessor! We may need to change the code to move them... can you see what work item type is causing the issue?

Update: From the logs, it looks like Shared Parameter is the problem.

[flavs97]

@MrHinsh Would it be possible to ignore this field Microsoft.VSTS.Common.ClosedDate somehow? What could be done to resolve this problem?

[MrHinsh]

This would be engineering work to resolve. There is only me and I have other priorities for now.

Funding for us doing engineering work like this is generally through 1) customer funding, or 2) donated free time.

Sponcer a Feature | Azure DevOps Migration Services