Need help creating configuation file for migrating an Azure Services project to Azure Server project

[bldcm]

Using version 16.0.4
We have been successful going TFS Server to ADO Server using the TfsTeamProjectEndpoint for source and target. When I change the URL to Azure Services I end up getting an exception as the utility tries to iterate through.

This led me to believe I needed to use the AzureDevOpsEndpoint type and the WorkItemTrackingProcess (WorkItemTrackingProcessorOptions) instead of the the TfsWorkItemMigrationProcessor. However, when I try this I get an exception:

Unable to cast object of type 'MigrationTools.Endpoints.AzureDevOpsEndpoint' to type 'MigrationTools.Endpoints.IWorkItemSourceEndpoint'

I've tried various other configurations, but above is the "closest" I have gotten to anything working. I have attached my configuration

This is my endpoint definition:
"SourceAzure": {
"EndpointType": "AzureDevOpsEndpoint",
"AccessToken": "*****************************",
"AuthenticationMode": "AccessToken",
"Organisation": "https://project.visualstudio.com",
"Project": "Source Project",
"ReflectedWorkItemIdField": "DUMMY.VALUE"
},

processor definition
{
"ProcessorType": "WorkItemTrackingProcessorOptions",
"Enabled": true,
"SourceName": "SourceAzure",
"TargetName": "Target",
configuration-sample.json

    "UpdateCreatedDate": true,
    "UpdateCreatedBy": true,
	"WIQLQuery": "SELECT [System.Id] FROM WorkItems WHERE [System.TeamProject] = @TeamProject AND [System.WorkItemType] NOT IN ('Test Suite', 'Test Plan') ORDER BY [System.ChangedDate] desc",
	"WIQLQuery": "SELECT [System.Id] FROM WorkItems WHERE [System.TeamProject] = @TeamProject AND [System.WorkItemType] IN ('Bug', 'User Story') AND [System.Id] IN (87) ORDER BY [System.ChangedDate] desc",
    "MaxGracefulFailures": 0,
    "SkipRevisionWithInvalidIterationPath": false,
    "SkipRevisionWithInvalidAreaPath": false,
    "Enrichers": null,
    "RefName": null,
    "ReplayRevisions": true,
    "CollapseRevisions": false,
	"LinkMigration": true,
	"AttachmentMigration": true,
	"StopMigrationOnMissingAreaIterationNodes": true		
  }

configuration-sample.json

[MrHinsh]

The AzureDevOpsEndpoint is only currently available for Process and Pipelines.

For work item migrations, TfsTeamProjectEndpoint is the correct option. What exception are you getting?

[bldcm]

The gist of the exception is "TF401326: Invalid field stauts 'InvalidNotOldValue' for field 'System.WorkItemType"

I am only migrating Bug and User Story types. There are some custom fields in these types of time string, int and picklist.

Full exception stack:

{"Timestamp":"2024-12-31T14:20:55.0056877-08:00","Level":"Error","MessageTemplate":"System.AggregateException: One or more errors occurred. --->
Microsoft.VisualStudio.Services.Common.VssServiceException: TF401326: Invalid field status 'InvalidNotOldValue' for field 'System.WorkItemType'.\r\n
at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.d__53.MoveNext()\r\n
--- End of stack trace from previous location where exception was thrown ---\r\n
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n
at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.d__51.MoveNext()\r\n
--- End of stack trace from previous location where exception was thrown ---\r\n
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n
at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.d__471.MoveNext()\r\n --- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.<SendAsync>d__281.MoveNext()\r\n
--- End of inner exception stack trace ---\r\n
at System.Threading.Tasks.Task1.GetResultCore(Boolean waitCompletionNotification)\r\n at MigrationTools.Processors.TfsWorkItemMigrationProcessor.ReplayRevisions(List1 revisionsToMigrate, WorkItemData sourceWorkItem, WorkItemData targetWorkItem)
in C:\Users\Connor.Dawson\Dev\Prod\ADO\ProdOps\VSTSSyncMigration\16.0.4_source\src\MigrationTools.Clients.TfsObjectModel\Processors\TfsWorkItemMigrationProcessor.cs:line 765\r\n
---> (Inner Exception #0) Microsoft.VisualStudio.Services.Common.VssServiceException: TF401326: Invalid field status 'InvalidNotOldValue' for field 'System.WorkItemType'.\r\n
at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.d__53.MoveNext()\r\n
--- End of stack trace from previous location where exception was thrown ---\r\n
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n
at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.d__51.MoveNext()\r\n
--- End of stack trace from previous location where exception was thrown ---\r\n
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n
at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.d__471.MoveNext()\r\n --- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.<SendAsync>d__281.MoveNext()<---\r\n
","TraceId":"8e7ed02dafc5d0c381048edf36cd644c","SpanId":"70c4161c71e8cad0","Properties":{"SourceContext":"MigrationTools.Processors.TfsWorkItemMigrationProcessor","versionString":"","targetWorkItemId":null,"sourceRevisionInt":32,"sourceWorkItemId":87,"totalWorkItems":1,"currentWorkItem":1,"sourceWorkItemTypeName":"Bug","ProcessId":4508}}

[MrHinsh]

I'm guessing here, but has the Work Item Type been changed for that work item?

[bldcm]

Yes, custom fields have been added to Bug and User Story, but we don't have access to the WITs like in ADO / TFS Server. Just the web client configuration for adding fields to the standard process selected at project creation time.

Can't even download WITs to get to the "nitty gritty" for this project.

What kind of change would cause that error?
Any way I can see which field in the work item is having the issue?

[bldcm]

The project is using an "Inherited Process Model"

[MrHinsh]

I was thinking that the work item was created as WorkItemTypeA and was later changed to WorkItemTypeB. We usually support that but something may have changed

[MrHinsh]

You can use the https://github.com/nkdAgility/azure-devops-automation-tools to download all of the nitty gritty for all the work item types..

[MrHinsh]

The field with the issue is System.WorkItemType

[bldcm]

With your scripts I was able to download the nitty gritty, which I have attached. We are using the "Escalations" process which looks like it was inherited from "Agile".

exception message: TF401326: Invalid field status 'InvalidNotOldValue' for field 'System.WorkItemType'.\r\n

Does this mean the status "InvalidNotOldValue" is not supported by this field? Just trying to understand why it is throwing an error so maybe we can fix it.

I don't know what the exception is really complaining about, but this is the field definition in the Bug which is the work item type I was testing with

              {
                  "referenceName":  "System.WorkItemType",
                  "name":  "Work Item Type",
                  "type":  "string",
                  "url":  "https://n-ppdf.visualstudio.com/_apis/work/processes/5928fc33-82cc-46da-b0cf-c203be743742/behaviors",
                  "customization":  "system",
                  "isLocked":  false
              },

AzureServicesProcessOutput.zip