[Bug]: TfsWorkItemTypeValidatorTool does not use the valueMapping defined in the FieldMappingTool

[sbouchexbellomie-Philips]

Version

• I confirm that I am using the latest version

Source Version

Azure DevOps Server 2019

Target Version

Azure DevOps Service

Relevant configuration

I have a FieldMappingTool configuration that maps a field to another and maps values as well.

Source field : F1
Target Field : F2

Mappings:
A -> A1
B -> B1

Relevant log output

[11:15:29 WRN] [16.3.2-Local.5]     Source field 'F1' and target field 'F2' have different allowed values.

and the debugger shows that source field values and target field values are different even they are mapped.

What happened?

When the TfsWorkItemTypeValidatorTool starts it complains that the fields do not have the value values.

Debug in Visual Studio

• Visual Studio Debug

[satano]

Please could you turn on debug logging and provider it? And also your field mapping tool configuration.

[sbouchexbellomie-Philips]

Configuration:

{
            "FieldMapType": "FieldValueMap",
            "sourceField": "Microsoft.VSTS.CMMI.Blocked",
            "targetField": "Microsoft.VSTS.CMMI.Blocked",
            "defaultValue": null,
            "valueMapping": {
              "Yes": "Yes",
              "No": ""
            },
            "ApplyTo": [
              "Task"
            ]
}

Logs:

Validating source field 'Microsoft.VSTS.CMMI.Blocked' (Blocked). 
[09:15:12 DBG] [16.3.2-Local.5]     Allowed values in target field do not match allowed values in source. Checking field value maps. 
[09:15:12 INF] [16.3.2-Local.5]     Missing values are: 'No' 
[09:15:12 WRN] [16.3.2-Local.5]       Value 'No' is mapped to '', which does not exists in target. This is probably invalid 'FieldValueMap' configuration. 
[09:15:12 WRN] [16.3.2-Local.5]     Source field 'Microsoft.VSTS.CMMI.Blocked' and target field 'Microsoft.VSTS.CMMI.Blocked' have different allowed values. 
[09:15:12 INF] [16.3.2-Local.5]       Source allowed values: 'No', 'Yes' 
[09:15:12 INF] [16.3.2-Local.5]       Target allowed values: 'Yes' 
[09:15:12 INF] [16.3.2-Local.5]       Missing values in target are: 'No'

[satano]

Thanks @sbouchexbellomie-Philips. Mapping to empty value really did not come to my mind. I will prepare PR later (probably today's evening) to handle this somehow.

Anyway, is it possible that you will update your process to contain No in allowed values for this field? I do not know what process do you use, but I tried in DevOps Agile process and the field Microsoft.VSTS.CMMI.Blocked contains both allowed values Yes and No. So maybe for some reason in your process the No value is removed. And maybe it is some other process, which really had only Yes and empty value means no. 🤷

[sbouchexbellomie-Philips]

Yes but it has been decided to remove the "No" value from the platform (not my decision)

[sbouchexbellomie-Philips]

@satano Please reopen the issue as it is also occuring with FieldToFieldMap configuration.

I have this configuration:

{ "FieldMapType": "FieldToFieldMap", "sourceField": "aaa.Approval.Approval1State", "targetField": "bbb.CII.ApproverStatus1", "defaultValue": null, "ApplyTo": [ "Test Case" ], "valueMapping": { "OK": "OK", "Not OK": "Rejected" } },

And I'm getting:
[12:11:01 WRN] [16.3.2-Local.5] Source field 'aaa.Approval.Approval1State' and target field 'bbb.CII.ApproverStatus1' have different allowed values.