Field Maps #2792
Replies: 2 comments 4 replies
-
Hello,
Could you please tell me if Am I doing something wrong? FYI: I've tried also this one and it does not work neither:
|
Beta Was this translation helpful? Give feedback.
-
Hello everyone, First of all, thank you so much to the team for creating and maintaining this amazing migration tool! I’ve been using it successfully for the past three months to migrate Work Items between ADO instances, and it worked almost flawlessly. Your efforts are truly appreciated. Recently, I tried performing another migration using the latest version of DevOpsMigrationTool, and I’ve run into some difficulties. My goal is straightforward: I want to migrate only work items (nothing else) from one ADO instance to another. I’ve carefully followed the updated documentation here: Field Mapping Tool Docs to set up the mappings correctly. In the error log, there are multiple errors, but I decided to focus on just one Work Item type (BUG) and configure it properly first. My hope is that once this one is fixed and no longer appears as a warning, I can move on to update the other mappings. Despite many attempts and trial-and-error adjustments to enable field mappings after each execution, I keep getting the same output. This leads me to think either my mappings are not being picked up even though it says Adding mapping or I’m missing something in the configuration. Additionally, I have tried the different SeriLog levels but I could not find anything there that points to concrete error. I would be very grateful if anyone could point me in the right direction—helping me identify where I might be going wrong and how to set up the configs properly. I have checked the discussion here and tried to update the config based on the answers found there as well. I understand there have been changes to both the Target and Source ADO, which now require additional adjustments and field mappings. My main issue and question revolve around this point. Below, I’ll attach my config and the output I get when running the tool. Initial config that worked three months ago: All WI which were newer then the fixed date were migrated without any issue. My latest config: Output: [14:10:49 INF] [16.2.11] No validator found for processor type TfsWorkItemOverwriteProcessorOptions Having setup the field mapping for BUG I was expecting not to see this warning: After reading the documentation, I initially assumed that this was just a warning related to the IS state, and that using the mapping config would resolve it properly. However, the migration doesn’t start at all and I get the following error: I would be extremely grateful if someone could guide me on what I might be missing or how to configure this correctly. Thank you so much in advance for your time and help—I truly appreciate it! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
This discussion is for questions, feedback, and community support related to the Field Maps.
Quick Reference
How to Use This Discussion
Related Documentation
Please refer to the official documentation for detailed configuration options and examples.
Beta Was this translation helpful? Give feedback.
All reactions