TfsWorkItemMigrationProcessor: The ClosedDate field Microsoft.VSTS.Common.ClosedDate on the Target does not exist in the source! #2990
Replies: 2 comments
-
|
I think that I may have found the answer in #2349. The "User Support" Work Item Type was "Disabled" in the target. I have enabled it and restarted the "TfsWorkItemMigrationProcessor". I will update if that resolves my issue. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Enabling the "User Support" Work Item Type has resolved the issue encountered with the "TfsWorkItemMigrationProcessor". |
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.
-
I am new to using the Azure DevOps Migration Tools and will appreciate any assistance.
Getting periodic errors that the "The ClosedDate field Microsoft.VSTS.Common.ClosedDate on the Target does not exist in the source!" when running the "TfsWorkItemMigrationProcessor".
We had created a new Azure DevOps Organization for the migration and created a new Process inheriting from the default "Agile" Process. Since the "ProcessDefinitionProcessor" did not run successfully, I created any missing "Work item types", "States", and "Rules", and also "Team configuration"->"Templates" in the target.
Do I need to disable Bypass for these Work Items or is there a bug that the ClosedDate is not mapping properly?
I have attached a copy of the Config file and log file.
Thank you very much in advance.
Config_20250916.txt
MigrationLog_20250916.txt
Beta Was this translation helpful? Give feedback.
All reactions