Replies: 2 comments 2 replies
-
Yeah, this is new! And we are still working through the valid scenario for all the users. I added an issue for some changes that I want to make. I'd defer to @satano as he created this tool, but he is on vacation and may not reply soon. I think that you're almost there: {
"CommonTools": {
"TfsWorkItemTypeValidatorTool": {
"Enabled": true,
"FixedTargetFields": {
"SomeWorkItemTypeName": [
{
"Custom.SomeSourceField0": "Custom.SomeTargetField0"
},
{
"Custom.SomeSourceField1": "Custom.SomeTargetField1"
},
{
"Custom.SomeSourceField2": "Custom.SomeTargetField2"
}
]
}
}
}
} This allows you to build a list of field maps for the validator. It will not move the data, but then it becomes your checklist for any field mapps that you need to add to the field mapping tool. |
Beta Was this translation helpful? Give feedback.
-
I gave that a try but didn't see any difference in the missing field validation logging. For now I can use the validation output to build a checklist but disable it for runs. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
First time trying to use v16. I have fields in my source that aren't in the target. I am handling this with FieldValueToTagMap so I want the validator to ignore these fields but I can't figure out how to do it so I had to disable the validator tool, which I'd rather not do. My config and log goes something like this (edited to anonymize). Should I be expecting something in the logs to indicate this is working?
Beta Was this translation helpful? Give feedback.
All reactions