Org to Org inherited process template sync

[GABecker]

I have setup ProcessDefinitionProcessor and able to sync fields between source and target. However, looking to update the process templates within an agile template (Epic, User Story, etc..). Some reason the process templates are not being updated. Do I need to use a different processor or am I missing steps within ProcessDefinitionProcessor .json. I wasn't able to find examples to help.

Here is what I am using to sync.
{
"Serilog": {
"MinimumLevel": "Information"
},
"MigrationTools": {
"Version": "16.0",
"Endpoints": {
"Source": {
"EndpointType": "AzureDevOpsEndpoint",
"AuthenticationMode": "AccessToken",
"AccessToken": "TokeNxyz",
"Organisation": "https://dev.azure.com/xyz",
"Project": "ProjectXYZ",
"ReflectedWorkItemIdField": ""
},
"Target": {
"EndpointType": "AzureDevOpsEndpoint",
"AuthenticationMode": "AccessToken",
"AccessToken": "TokeNxyz",
"Organisation": "https://dev.azure.com/123",
"Project": "ProcessMigTest",
"ReflectedWorkItemIdField": ""
}
},
"Processors": [
{
"ProcessorType": "ProcessDefinitionProcessor",
"Enabled": true,
"Processes": {
"TestAgile.Epic": [
"Epic"
]
},
"ProcessMaps": {
"TestAgile": "TestAgile"
},
"UpdateProcessDetails": true,
"MaxDegreeOfParallelism": 0,
"SourceName": "Source",
"TargetName": "Target"
}
],
"CommonTools": {
"FieldMappingTool": {
"Enabled": true,
"FieldMaps": [
{
"FieldMapType": "FieldToFieldMap",
"sourceField": "",
"targetField": "",
"defaultValue": "",
"ApplyTo": ["*"]
}
]
},
"TfsChangeSetMappingTool": {
"Enabled": true,
"ChangeSetMappingFile": ""
},
"TfsGitRepositoryTool": {
"Enabled": true,
"Mappings": null
}
}
}
}

[MrHinsh]

@GABecker I did not create ProcessDefinitionProcessor as it was a contribution by @akanieski and I'm not sure of the intent... it may be that the original intent was one-time migration, and not sync.

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

Sponcer a Feature | Hire us directly

[GABecker]

@MrHinsh do you have any suggestions or other processors that support process template sync? It wouldn't need to be a two-way sync but source to target. We would like to have a primary ORG act as the standard for all others. Any changes to it will be deployed which would include fields and any associated template change within Agile, Scrum, CMMI, etc.. Any guidance is appreciated.

[MrHinsh]

I wrote some tooling and created a build component some years ago that allowed a customer to have a single "source of truth" and then port the process all around the org in Rings based on risk.

https://marketplace.visualstudio.com/items?itemName=nkdagility.processtemplate

I've not used them in a blue moon, but I have customers that still use them. And it looks like 2.5k installs still.

[akanieski]

Are there any error messages when you run the processor? Also, can you clarify what specifically is not synchronizing? You mentioned fields are synchronizing fine. So what specifically is not synchronizing, Is it entire types not moving over? Or is it Rules/States/Behaviors?

[akanieski]

I can't tell from that if it's failing on the next WorkItemTypeField or if its failing on what comes after WorkItemTypeField's which is all the WorkItemRule followed by all the other behaviors, pages and layout details.

If you clone the repo, and get it running from Visual Studio, you will get line items and you will see specifically where it is failing.

Have you got yourself setup from VS?

[GABecker]

@akanieski
I am running it from powershell running this command.

devopsmigration.exe execute -c "c:\ado-migration\sync.json"

I have VS but have not used it for this.

[akanieski]

if you download the latest source code. Open VS.. and then:

Find the devopsmigration.exe process, and then attach.

the timing might be challenging if it moves very quickly to the error state.

[GABecker]

@akanieski ,

Had some help from @jbrown9100 to debug. Still have not figured out the issue other than it is trying to update a system field it should bypass (System.IterationID). In AzureDevOpsEndpoint.cs its erroring around line 444.

[GABecker]

@akanieski,
We did more debugging and found its failing when trying to update the WorkItemTypeField System.InterationID. @jbrown9100 was able to help track it down and may provide help with fixing it.

What we found is that the payload to update the field is incorrect. This is what is being passed.

{"referenceName":"System.IterationId","allowedValues":[],"allowGroups":false,"readOnly":false}

I could get it working outside of the migrator by adding "required": true,.

I also don't know that what is being passed is correct. If you look at the field parameters what should be passed is something that looks like this.
{"referenceName": "System.IterationId","name": "Iteration ID","type": "integer","required": true,"customization": "system","isLocked": false}

BTW.. I played around with it and found that I could push an update by only passing the "required": true. parameter. However, if the parameter wasn't passed nothing would update.