Tfs WorkItemType Validator Tool

[MrHinsh]

This discussion is for questions, feedback, and community support related to the TFS Work Item Type Validator Tool.

Quick Reference

• Class Name: TfsWorkItemTypeValidatorTool
• Friendly Name: Tfs Work Item Type Validator
• Documentation: TFS Work Item Type Validator Tool

How to Use This Discussion

• Ask Questions: If you need help configuring or using this component
• Share Examples: Post your configuration examples or use cases
• Report Issues: Describe any problems you encounter (though bugs should be reported as GitHub Issues)
• Request Features: Suggest improvements or new features

Related Documentation

Please refer to the official documentation for detailed configuration options and examples.

[chaurenservices]

Hello,

Do you have an example of how to properly use the ExcludeSourceFields Parameter?

In my config file, I had tried this example:

    "CommonTools": {
        "TfsWorkItemTypeValidatorTool": {
            "Enabled": true,
            "ExcludeSourceFields": {
                
                    "User Story":"Custom.HoursofEffort"
                    
        }
 }

}

But I still get warnings in my logs about this Source field being missing in my Target. I'd like to skip validating this Custom.HoursofEffort in the Target:
[12:21:12 INF] [16.3.1] Validating work item type 'User Story'
[12:21:12 WRN] [16.3.1] Missing field 'Custom.HoursofEffort' in 'User Story'.
[12:21:12 INF] [16.3.1] Source field reference name: Custom.HoursofEffort
[12:21:12 INF] [16.3.1] Source field name: Hours of Effort
[12:21:12 INF] [16.3.1] Field type: Double
[12:21:12 INF] [16.3.1] Allowed values:
[12:21:12 INF] [16.3.1] Allowed values type: Double

[MrHinsh]

@satano can we get the docs updated :) I think it still has the old format

[satano]

I will look at it.

[satano]

Update TfsWorkItemTypeValidatorTool documentation: #3055

[chaurenservices]

Thanks @satano. That makes more sense with the array to have multiple excluded fields.

Any advice if I'm still coming across the same error messages after updating my config to match this format?

[chaurenservices]

@satano , I just upgraded to the production 16.3.3 and that seems to have resolved the issue for me now. Thank you so much for your help!