TfsWorkItemEmbeddedLinkTool is disabled but still working

[gyaaanu]

I am running migration for project with around 15k workitems, we also want to retain the history of the workitems, retaining all the revisions.
while migration we faced issue with the iteration mapping so we mapped them to legacy archive iteration for the history iterations only,
another issue we faced was due to response failure from the target user api, used for mentions in the description and comments to fix it we disabled the processor TfsWorkItemEmbeddedLinkTool but it is still working for the revisions, the EmbededImagesRepairEnricher, TfsWorkItemEmbededLinkTool is also running, each timing out for 5 minutes

I am also getting an error saying "Dates must be increasing" I am unable to trace this issue, why it occured.
we are working to migrate 30+ services and solving these blockers are essential, response from the team is Appreciated.

[MrHinsh]

That seasm like a lot in one go... and it would be helpfull to know if you are using TFS/ADO and what version and where.

I am also getting an error saying "Dates must be increasing" I am unable to trace this issue, why it occured.

This is a known bug in the TFS Object Model... I dont have a work around for it other than to skip that work item. I belive its a race conduction, but the API's are EOL.

https://github.com/nkdAgility/azure-devops-migration-platform wuill resolve this but its still expermimental.

esponse failure from the target user api,

This hsould not be the case, have you reported it to Microaoft?

[gyaaanu]

16.3 TFS migration, One more issue I am facing is I want to migrate 15k WITs for 1 service and we have multiple services. The issue I am facing is regarding the missing area path and missing iteration path, If possible I don't want to migrate the history of the work item. Only the current state will work, but even after setting the replayRevisions as false it still says missing nodes for areas and iteration. I want a work around to avoid repeatedly manual mapping of the area and iteration mapping. I am working on migration for MS internal teams, for the One project we don't have option to make new iterations we can just map with the existing iteration path with the overlapping match from source to target.
Help me fix this issue. Is it possible to only migrate the current state or work item without the history of it like the revisions are causing the issue apparently. Or is there any other work around. Let me know if you need more information to work on.

[gyaaanu]

I was working on a tool wrapping the nkdagility tool in it, for complete migration including work items, teams, repo, feeds, pipelines.
using the asure APIs and python and powershell.

[gyaaanu]

I have one more doubt, when migrating workitems under an area path the revisions show multiple area paths missing and same for iteration paths, is there a way to map all the different area path to one single archive path and the correct area path is mapped properly. For iteration path also I have some iteration mapped for like 6 month rest should be mapped to a specific legacy or archived iteration path. Hope you provide a solution for this doubt.