How to migrate Closed Items

[mmenninghaus]

It ist not possible to migrate Closed Items. When I include them in my query it reads

System.Web.Services.Protocols.SoapException: VS403417: ChangedBy value cannot be empty when BypassRules is specified

According to System.Web.Services.Protocols.SoapException: VS403417: ChangedBy value cannot be empty when BypassRules is specified

it should be possible to explicitly bypass the rules. In addition, my log also reads for both, source and target organization.

[v14.3.7] TfsWorkItemMigrationClient::GetWorkItemStore(https://dev.azure.com/[organization name removed], BypassRules)

What am I missing here?

[MrHinsh]

You should check your Source environment and see what is stored in the "ChangedBy" field.

Even with BypassRules enabled, there are a set of things that MUST always be true:

1. ChangedBy must not be empty
2. Area and Iteration paths must be valid
3. Dates must be valid

Any of these items being broken will generate a SOAP error.

[MrHinsh]

@mmenninghaus, you can't migrate items that have no closedby value. It should not be possible to have them.

Its also not possible to update a work item without triggering notifications without turning them off.

Which version of TFS do you have?

ChangedBy is not a field that you can update. Its a system data on which account made the change. It MUST always have a value.

[mmenninghaus]

@MrHinsh I double checked. The closed items in question have "Changed By", "Changed Date", "Iteration Path" and "Closed By" set and valid. We still get the errors mentioned above.
It seems to me that the only difference between items that can and can not be migrated is the "Closed By" value. Items, which are closed and have the value for "Closed by" set can not be migrated.
-> Has anyone ever migrated closed items? Maybe there is a reason for excluding the closed items in the default query.

[MrHinsh]

I migrate closed items with every migration.

You may need to debug in Visual Studio with your data to see why, in your circumstance, the Changed By field is blank. We can help with debugging; it's billed based on time with no guaranteed resolution.

[MrHinsh]

Can you post your config?

[mmenninghaus]

{
"ChangeSetMappingFile": null,
"Source": {
"$type": "TfsTeamProjectConfig",
"Collection": "https://dev.azure.com/[Placeholder]/",
"Project": "[Placeholder]",
"ReflectedWorkItemIDFieldName": "Custom.ReflectedWorkItemId",
"AllowCrossProjectLinking": false,
"AuthenticationMode": "AccessToken",
"PersonalAccessToken": "[Placeholder]",
"LanguageMaps": {
"AreaPath": "Area",
"IterationPath": "Iteration"
}
},
"Target": {
"$type": "TfsTeamProjectConfig",
"Collection": "https://dev.azure.com/[Placeholder]",
"Project": "[Placeholder]",
"ReflectedWorkItemIDFieldName": "Custom.ReflectedWorkItemId",
"AllowCrossProjectLinking": false,
"AuthenticationMode": "AccessToken",
"PersonalAccessToken": "[Placeholder]",
"LanguageMaps": {
"AreaPath": "Area",
"IterationPath": "Iteration"
}
},
"FieldMaps": [],
"GitRepoMapping": null,
"LogLevel": "Information",
"CommonEnrichersConfig": null,
"Processors": [
{
"$type": "WorkItemMigrationConfig",
"Enabled": true,
"ReplayRevisions": true,
"PrefixProjectToNodes": false,
"UpdateCreatedDate": true,
"UpdateCreatedBy": true,
"WIQLQueryBit": "AND [System.WorkItemType] NOT IN ('Test Suite', 'Test Plan','Shared Steps','Shared Parameter','Feedback Request')",
"WIQLOrderBit": "[System.ChangedDate] desc",
"LinkMigration": true,
"AttachmentMigration": true,
"AttachmentWorkingPath": "c:\temp\WorkItemAttachmentWorkingFolder\",
"FixHtmlAttachmentLinks": false,
"SkipToFinalRevisedWorkItemType": false,
"WorkItemCreateRetryLimit": 5,
"FilterWorkItemsThatAlreadyExistInTarget": true,
"PauseAfterEachWorkItem": false,
"AttachmentMaxSize": 480000000,
"AttachRevisionHistory": false,
"LinkMigrationSaveEachAsAdded": false,
"GenerateMigrationComment": true,
"WorkItemIDs": null,
"MaxRevisions": 0,
"UseCommonNodeStructureEnricherConfig": false,
"NodeBasePaths": null,
"AreaMaps": {},
"IterationMaps": {},
"MaxGracefulFailures": 0,
"SkipRevisionWithInvalidIterationPath": false,
"SkipRevisionWithInvalidAreaPath": false,
"ShouldCreateMissingRevisionPaths": true,
"ShouldCreateNodesUpFront": true
}
],
"Version": "14.3",
"workaroundForQuerySOAPBugEnabled": false,
"WorkItemTypeDefinition": {
"sourceWorkItemTypeName": "targetWorkItemTypeName"
},
"Endpoints": {
"InMemoryWorkItemEndpoints": [
{
"Name": "Source",
"EndpointEnrichers": null
},
{
"Name": "Target",
"EndpointEnrichers": null
}
]
}
}

[MrHinsh]

Hmm, there must be a circumstance that the Changed By field gets emptied for you.

Can you debug one of the work items in Visual Studio that is the issue? You can add the ID to the query to load just hat work item.

[mmenninghaus]

I debugged it intensively, but could not really find the root cause.
In the end, I first migrated the items into a project with the very same process settings and then inside the target organisation into the correct project.