Dealing with custom LinkTypes

[DEW-Consulting]

I'm currently using the migrator to relocate ~33k work items, on-premise DevOps 2019, from a source project using a customized XML process model to a new project using an Inherited process model. The XML process model has 3 custom LinkTypes that are widely used across the work items. While the migration is going great (with all the other migration customizations I've handled in the config file), it appears that the LinkMigration component is skipping over the custom LinkTypes - unsure how to handle them.

I'm not sure if the LinkMigration already has a config option to deal with custom LinkTypes, or how I would be able to configure it if it does. As a side note, if I have ReflectedWorkItemIDFieldNames on both source and target, if there's a way to re-run the LinkMigration exclusively to just update the skipped links.

[MrHinsh]

Custom link types are not supported in Azure DevOps and thus would be skipped.

How would you like Custom link types to be handled? We need to take into account that they could be "Related", "Hierarchy", or "Parent Child" base types... Do you know which ones you have?

[DEW-Consulting]

Thanks - it's good to know I'm not missing anything then. I'll have to resort to manual creation in meantime.

An example of one of the primary LinkTypes we use is:
<LinkType ReferenceName="Organization.Results" ForwardName="Results In" ReverseName="Results From" Topology="Dependency" />

What would be nice is if I could either set a flag to just convert all custom LinkTypes to a specific, supported LinkType in DevOps... or if there was an equivalent functionality as FieldtoFieldMapConfig, where I could instruct the migrator on which custom LinkType I wanted converted to which supported target LinkType.

At any rate, thank you so much for this tool - it's been a huge time saver in helping us convert over into DevOps.

[Sageatahan]

Thanks - it's good to know I'm not missing anything then. I'll have to resort to manual creation in meantime.

An example of one of the primary LinkTypes we use is:
<LinkType ReferenceName="Organization.Results" ForwardName="Results In" ReverseName="Results From" Topology="Dependency" />

What would be nice is if I could either set a flag to just convert all custom LinkTypes to a specific, supported LinkType in DevOps... or if there was an equivalent functionality as FieldtoFieldMapConfig, where I could instruct the migrator on which custom LinkType I wanted converted to which supported target LinkType.

At any rate, thank you so much for this tool - it's been a huge time saver in helping us convert over into DevOps.

I am having a similar issue, did you end up finding a solution?
Thanks