Error while running TfsTestPlansAndSuitesMigrationProcessor

[alvimrodrigo]

I'm migrating our old Azure DevOps on premise, which was upgraded from TFS to the new Azure Devops, using this tool.
As there are only 4 projects, I migrated the repos using git clone -mirror, and restructured the CI/CD pipeline to a new yaml standard (previously legacy).
This way, I am only using test plans to migrate in our configration.json using the following processor:

{ "ProcessorType": "TfsTestPlansAndSuitesMigrationProcessorOptions", "Enabled": true, "TestPlanQuery": null, "RemoveAllLinks": false, "MigrationDelay": 0, "RemoveInvalidTestSuiteLinks": false, "FilterCompleted": false, "SourceName": "Source2", "TargetName": "Target2", "RefName": null }

I was able to access the servers, however, when uploading the plans to the new Azure Devops, the following error returns:
Microsoft.TeamFoundation.WorkItemTracking.Client.FieldDefinitionNotExistException: TF26027: A tfs_test_plans.ReflectedWorkItemId field definition in the work item type definition file does not exist.

The old project at TFS used the Agile process, and I created the same in the current one.
I've already tried using managed, using the prefix as Custom, as Agile, as Agile_TFS as per print, I also tried to create a new one from Agile and created a new field with the name tfs_test_plans and tfs_migrate, which also didn't work, as per print.
Have you ever experienced something similar, is there a known solution?

n Microsoft.TeamFoundation.WorkItemTracking.Client.FieldDefinitionCollection.get_Item(String name) at Microsoft.TeamFoundation.WorkItemTracking.Client.FieldCollection.get_Item(String name) in MigrationTools.Processors.TfsTestPlansAndSuitesMigrationProcessor.AssignReflectedWorkItemId(Int32 sourceWIId, Int32 targetWIId) in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Processors\TfsTestPlan sAndSuitesMigrationProcessor.cs :line 364 in MigrationTools.Processors.TfsTestPlansAndSuitesMigrationProcessor.ProcessTestPlan(ITestPlan sourcePlan) in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Processors\TfsTestPlansAndSuitesMigrationProcessor.cs:line 867 in MigrationTools.Processors.TfsTestPlansAndSuitesMigrationProcessor.InternalExecute() in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Processors\TfsTestPlansAndSuitesMigrationProcessor.cs: line 113 in MigrationTools.Processors.Infrastructure.Processor.Execute() in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools\Processors\Infrastructure\Processor.cs:line 98

[alvimrodrigo]

I'll try the steps I saw in this discussion here, if anything I'll open another topic so we can discuss or show that it worked to help other people.

#2049

[alvimrodrigo]

I reopened the discussion, in case anyone can help me on this topic.
It was not possible to perform the steps in the link I sent, it seems to only work on an old version of the tool. Can you help me with what it could be?

[alvimrodrigo]

But I need the RefName of the target project's ReflectedWorkItemId, right?
Even though I carefully follow the steps to migrate the testplans, I always get this ReflectedWorkItemID error.
Can you help me with which prefix I should put in the json to do the migration?
Thanks!

[17:18:46 WRN] [16.0.3] ValidatingRequiredField: Test Case does not contain Agile_TFS.ReflectedWorkItemId
[17:18:46 WRN] [16.0.3] ValidatingRequiredField: Shared Parameter does not contain Agile_TFS.ReflectedWorkItemId
[17:18:46 WRN] [16.0.3] ValidatingRequiredField: Shared Steps does not contain Agile_TFS.ReflectedWorkItemId
[17:18:46 ERR] [16.0.3] Not all work items in scope contain a valid ReflectedWorkItemId Field!
Microsoft.TeamFoundation.WorkItemTracking.Client.InvalidFieldValueException: Not all work items in scope contain a valid ReflectedWorkItemId Field!

[MrHinsh]

If you open a work item and go to the field, edit it, and then go to the second tab it will show the refname of the field. This is what you need.

Follow this. From the process menu in the admin.

[alvimrodrigo]

I found it here, in the test case the 'Field Reference Name' field is as 'Microsoft.VSTS.TCM.Steps' and Test Plans and Suits are as System.Description
I need to change it, given the process I'm going to run, right?

[alvimrodrigo]

I'm getting this same error by including the ReflectedWorkItemId prefix
[19:17:43 WRN] [16.0.3] ValidatingRequiredField: Test Case does not contain Microsoft.VSTS.TCM.Steps.ReflectedWorkItemId [19:17:43 WRN] [16.0.3] ValidatingRequiredField: Shared Parameter does not contain Microsoft.VSTS.TCM.Steps.ReflectedWorkItemId [19:17:43 WRN] [16.0.3] ValidatingRequiredField: Shared Steps does not contain Microsoft.VSTS.TCM.Steps.ReflectedWorkItemId [19:17:43 ERR] [16.0.3] Not all work items in scope contain a valid ReflectedWorkItemId Field! Microsoft.TeamFoundation.WorkItemTracking.Client.InvalidFieldValueException: Not all work items in scope contain a valid ReflectedWorkItemId Field!

[alvimrodrigo]

I'm using this processor and this Field from the projects for the migration.

   "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') ORDER BY [System.ChangedDate] desc",
        "SourceName": "Source2",
        "TargetName": "Target2"     
      }
    ]

"ReflectedWorkItemIdField": "Microsoft.VSTS.TCM.Steps.ReflectedWorkItemId",

[alvimrodrigo]

[17:04:06 DBG] [16.0.3] ValidatingRequiredField: Test Case contains Microsoft.VSTS.TCM.Steps
[17:04:06 WRN] [16.0.3] ValidatingRequiredField: Shared Parameter does not contain Microsoft.VSTS.TCM.Steps
[17:04:06 DBG] [16.0.3] ValidatingRequiredField: Shared Steps contains Microsoft.VSTS.TCM.Steps

I was able to point to the correct prefix, however, there is a problem in Shared Steps or Shared Parameter, can you help me?

[alvimrodrigo]

I adjusted the queries, adjusted the processors, and used everything according to the official documentation and it worked! I apologize and thank you. Ending here.
Everything is here:
https://nkdagility.com/learn/azure-devops-migration-tools/getstarted/
Just adapt to the new version and it worked.