-
Hi, Hopefully someone can shed some light on the issue that I am seeing. I have ran a full work item sync using WorkItemMigrationContext processor and a few weeks later decided to run another sync to get any changes made to work items in source across to the target. I have noticed that changes would not get across to the target ado. My processor configuration: {
"$type": "WorkItemMigrationConfig",
"Enabled": true,
"UpdateCreatedDate": true,
"UpdateCreatedBy": true,
"WIQLQuery": "SELECT [System.Id] FROM WorkItems WHERE [System.TeamProject] = @TeamProject AND [System.WorkItemType] NOT IN ('Test Suite', 'Test Plan','Shared Steps','Shared Parameter','Feedback Request') AND [System.Id] = '116475' ORDER BY [System.ChangedDate] desc",
"FixHtmlAttachmentLinks": false,
"WorkItemCreateRetryLimit": 5,
"FilterWorkItemsThatAlreadyExistInTarget": false,
"PauseAfterEachWorkItem": false,
"AttachRevisionHistory": false,
"GenerateMigrationComment": true,
"WorkItemIDs": null,
"MaxGracefulFailures": 0,
"SkipRevisionWithInvalidIterationPath": false,
"SkipRevisionWithInvalidAreaPath": false
}, The message that I see in the console is:
|
Beta Was this translation helpful? Give feedback.
Answered by
MrHinsh
Sep 30, 2024
Replies: 1 comment 2 replies
-
The revisions in-between are likely older than the latest revision on the target. This is likely due to the attachment and link saves... |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Yes, if the source is edited newer than the last edit on the target it will pull.