Replies: 1 comment
-
1 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I'm currently using azure-devops-migration-tools and facing an issue where the UpdateCreatedBy setting seems to have no effect. Despite setting it to true, the CreatedBy field of the migrated work items is not being updated.
Here’s the relevant section of my configuration:
"Processors": [
{
"ProcessorType": "TfsWorkItemMigrationProcessor",
"Enabled": true,
"ReplayRevisions": true,
"UpdateRevisionBy": true,
"UpdateCreatedDate": true,
"UpdateCreatedBy": true,
"Force": true,
"FilterWorkItemsThatAlreadyExistInTarget": false,
"WorkItemCreateRetryLimit": 10,
"PauseAfterEachWorkItem": false,
"WIQLQuery": "SELECT [System.Id] FROM WorkItems WHERE [System.TeamProject] = @teamproject",
"SkipRevisionWithMissingReflectedWorkItemId": true,
"FixHtmlAttachmentLinks": true,
"MaxGracefulFailures": 2,
"SkipRevisionWithInvalidIterationPath": false,
"SkipRevisionWithInvalidAreaPath": false,
"GenerateMigrationComment": false,
"SourceName": "Source",
"TargetName": "Target"
}
]
Things I’ve already checked:
The Force option is set to true, so I expect the CreatedBy field to be updated.
I’ve verified that the user performing the migration has sufficient permissions on the target project.
I’m using the latest version of the migration tool.
However, the CreatedBy field is still not being updated on the target work items. Can anyone suggest why this might be happening, or if there’s something I’m missing?
Thank you in advance!
Beta Was this translation helpful? Give feedback.
All reactions