Cross-project Parent links not established when migrating with download option 0 about jira-azuredevops-migrator

[Alexander-Hjelm]

Related to #745?

[GeethikaKrishnan]

If I'm not wrong, #745 seems to be an issue with linking sub-tasks to tasks as there is no defined link mapping.

Here I am trying to migrate with download options 0 so that no other issues (issues not in migration query) get migrated.
I am trying to migrate two separate projects with cross-linked items.

If these items that are migrated in two phases, and the second phase of the migration contains Epic links to the issues in first phase of the migration, the links do not get established even after both migrations are done.

[Alexander-Hjelm]

Ok! Have you seen and followed out guidelines when it comes to migrating multiple projects in sequence with download-options = 0? See: https://github.com/solidify/jira-azuredevops-migrator/blob/master/docs/faq.md#scenario-2-multiple-projects

[GeethikaKrishnan]

Yes, I've looked into this and as per the instructions,
I've used separate config files and separate workspace folder for each migration.
I've relocated the itemsJournal.txt file into the workspace folder for the next migration.
I have not used the --force flag.
Is there anything else I should be doing or something I've missed?

[Alexander-Hjelm]

Ok! We will have to look into it. Sounds like something fishy could be going on here with how links are interpreted. Marking as bug.

I assume that you have mapped the Child link type as well as the Parent Link type in your config?

[GeethikaKrishnan]

Yes. I've attached the config for both the migrations which contains the mappings