Work Item Type Capitalization / Missing mapping issue

[StainlessSteelDream]

I'm getting some odd work item mapping errors, seeing the same Work Item Type with different capitalization being found (see bloew)

21:07:51 WRN] [v14.4.6] Validating::WorkItemTypes::targetWorkItemTypes::There are 3 WorkItemTypes that are used in the history of the Source and that do not exist in the Target. These will all need mapped using WorkItemTypeDefinition in the config.
[21:07:51 WRN] [v14.4.6] Validating::WorkItemTypes::targetWorkItemTypes::New Feature::Mapped? False
[21:07:51 WRN] [v14.4.6] Validating::WorkItemTypes::targetWorkItemTypes::New feature::Mapped? True
[21:07:51 WRN] [v14.4.6] Validating::WorkItemTypes::targetWorkItemTypes::Product Backlog Item::Mapped? True

but odder on the source project witadmin listwitd command does not show these work item types at all. At some time in the past the "New feature" work item type was renamed using the witadmin command, but the history seems to have the old name (2 names?) in it.

Anyone have a suggestion on what I can put in the config file to address this, or how to cleanup the wit items in the source?

I cannot use:
"WorkItemTypeDefinition": {
"Product Backlog Item": "User Story",
"New feature": "Feature",
"New Feature": "Feature",
},
as this gives a "A duplicate key 'WorkItemTypeDefinition:New Feature' was found."error

Thanks

[StainlessSteelDream]

witadmin listwitd /collection:----
Bug
Code Review Request
Code Review Response
Feedback Request
Feedback Response
Task
Test Case
Issue
User Story

[MrHinsh]

I wonder if just making the checks case insensitive will fix this!

[MrHinsh]

This is a mismatch between the Jsonconvertor and .net native dictionaries.

[prasanthimalepati]

I am also facing the same issue.

[prasanthimalepati]

Is there any solution for this?