Advanced Roadmaps failing ('We couldn't export Person' -> Entity mri:mig:jira/advancedroadmaps:team:xx is expected to be exported, but it was not')

Issue Summary

This is reproducible on Data Center: yes

Steps to Reproduce

1. Create a project and a board associated to it
2. Link the board as an issue source to an AR plan
3. Create a team within the AR plan to work on the board
4. Assign persons to this team
5. Migrate only the project at first
6. Create another migration with AR plans this time
7. Remove the project from "Project already exist in cloud" preflight
8. Continue with the migration

Expected Results

AR plans, persons, teams are migrated successfully

Actual Results

The below exception is thrown in the CROSS-PROJECT-DATA.log file:

We couldn't export Person 929. Reason: java.lang.IllegalStateException: Entity mri:mig:jira/advancedroadmaps:team:XXX is expected to be exported, but it was not. 

AR plans fail to migrate

Workaround

Disclaimer - The following workaround may require huge effort to un link and re link data before and after migration.

 1. Run the below query on the server instance - 

SELECT AO_D9132D_ISSUE_SOURCE.PLAN_ID, SOURCE_TYPE, SOURCE_VALUE, TEAM_ID,  REQCONTENT as filterJQL  from AO_D9132D_ISSUE_SOURCE join AO_D9132D_PLANTEAM on ISSUE_SOURCE_ID=AO_D9132D_ISSUE_SOURCE.ID join AO_60DB71_RAPIDVIEW on SOURCE_VALUE=AO_60DB71_RAPIDVIEW.ID join SEARCHREQUEST on SEARCHREQUEST.ID=SAVED_FILTER_ID where SOURCE_TYPE='Board' order by TEAM_ID 

2. Before making any changes, capture the above query result somewhere as it would be absolutely necessary to relink data post migration.

3. For every team_id, make sure that 1 team_id works on at max 1 board. If not, un-assign team from the boards using UI ( ar-plan -> teams ) and make it at max 1 board.

4. Run the query in step 1 to get the updated results. (You don't need to capture this information for later usage)

5. Every team in the query result should be working on 1 board at max.

6. For every row in the query result, check the filterJQL column. Look at the project(s) it references.

   6a. If at least there is one project key which is not pre migrated to cloud, no changes required.

   6b. If all the referenced project keys are pre migrated, un-assign the team from this board ( ar-plan -> teams -> edit -> associated issue source -> None -> Save ).

   6c. If there is no project referenced by the board, un-assign the team from this board. 

   6d. Make sure to save these changes to jira.

7. Now run the migration, it should succeed. (Remove the conflicting projects in preflight checks which are present in cloud)

8. Post migration, go through saved query result from step 1 and verify in cloud-

   8a. If the board is present in cloud, make sure its linked to the appropriate ar plan(s). 

   8b. If the board is not present in cloud, create them in cloud and link to the appropriate ar-plan(s). 

   8c. Use the reference of the saved result from step 1 to re-link data appropriately in cloud. Also make use of the result to assign teams to work on the appropriate board(s).