Hardcoded ReflectedWorkItemIDFieldName on WorkItemUpdate processor and misleading documentation #1347
sonicadv27
started this conversation in
General
Replies: 1 comment
-
The characters I would assume that the config file that is being passed includes The Processor will indeed update work items on the Target from the Source. You can Migrate work items and then rerun the migration to make additional changes since the last migration. Could you specify precisely what it is that you are trying to do? |
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.
-
The ReflectedWorkItemIDFieldName seems to be hardcoded on the WorkItemUpdateConfig processor as TfsMigrationTool.ReflectedWorkItemId.
When doing an Azure DevOps to Azure DevOps work item update, the ReflectedWorkItemId we created uses the "Custom" tag, so the resulting field name is Custom.ReflectedworkItemId. However, when running the WorkItemUpdateConfig, any query fails with
TF51005: The query references a field that does not exist. The error is caused by «[TfsMigrationTool.ReflectedWorkItemId]»
This field doesn't exist anywhere on the Source or the Target and no matter the configuration i use the end result of the command is this error.
Also, I've been trying to use the processor do update work items on Target with data from Source and after searching online it seems that's not its purpose. The documentation however makes it seem like you can update work items from Source into Target so it should be updated to more clearly state its scope.
Beta Was this translation helpful? Give feedback.
All reactions