Is there a way to map non-standard work item relationships?

[bldcm]

We are migrating from TFS to ADO, currently using version 14, but moving to 16. This problem exists in both versions as far as we can tell.

SOME of our TFS work items have link types that do not exist in ADO and we don't want to create these in ADO because we want to normalize to a standard.

Is there a way to say that if a link fails because the target does not have a link type matching the source to just use a default like type, like "Related"?

Side note, when I do a query between source and target and tell there is a discrepancy based on the reported "Related Link Count", but the log of the tool does not reflect the number of WIs with missing links.

[MrHinsh]

This is certainly a gap! Ive created #2429 and it will require some dev work, and a new TfsLinkTypeMappingTool added to the mix...

Funding for us adding new features like this is generally through 1) customer funding, or 2) donated free time.

Sponcer a Feature

[bldcm]

Thanks, I will send this up to management and see if I can get some support sent your way. What is a typical support amount for something like this?

[MrHinsh]

For this sort of tool it would likely be around £3000 GBP delivered in the latest version.