AllowCrossProjectLinking - How does it work?

[0-0-1-0-1-0-1-0]

Here is the scenario for my migration.

Project A:

• Sub area path 1
• Sub area path 2
• Sub area path 3 <- Source Area path I want to move OUT of the project into a new Project B.
  *This sub area and its related work items have links to Project A, Project C, Project D, Project E etc.

When I migrate these work items from Project A - Sub Area Path 3 to brand new Project B, will all the links be migrated as well that point to items in Project C, Project D, Project E, etc.?

All projects are in the same organization.

We have projects where multiple teams are working under but its not their project and we want to give them their own space to manage their work and code.

[0-0-1-0-1-0-1-0]

This is the error i get:

[12:22:28 INF] Migrating link for 28985 of type RelatedLink
[12:22:28 INF] [SKIP] Unable to migrate link where Link of type System.LinkTypes.Hierarchy-Forward where wiSourceL=28985, wiSourceR=75202, wiTargetL=119631, wiTargetR=75202 as target WI has not been migrated

I want to make sure that all links are migrated, this works fine for work items moving from Project A to Project B, but any links that point to Project C/D/E/F fail to migrate.

How do i get say on the final sync/migration run to FORCE the links to migrate?

[0-0-1-0-1-0-1-0]

Any help/info would be greatly appreciated.

[0-0-1-0-1-0-1-0]

Bump. Checking again to see if any clarification can be provided on how the cross project linking works.