Issue Summary
Data integrity checks within the migration flow causes sprint board associations stored on table/column "AO_60DB71_SPRINT"."RAPID_VIEW_ID" to not migrate as expected. This happens because the data integrity checks can overwrite specific data that impact the sprint board association to a null value when certain conditions are met.

Steps to Reproduce

1. On data center you have 2 projects, Project A and Project B
2. Create a board and sprint (Sprint A) that includes only Project A
3. Put a Jira issue (PROJA-1) from Project A into Sprint A.
4. Now change the filter for Sprint A to a filter that only includes Project B.
5. PROJA-1 has Sprint field = Sprint A, but PROJA-1 is no longer showing in Sprint A (because the filter was changed).
6. Now migrate Project B then Project A

Expected Results
The Sprint in "AO_60DB71_SPRINT" has a valid "RAPID_VIEW_ID".

Actual Results
The Sprint in "AO_60DB71_SPRINT" has "RAPID_VIEW_ID" as null because PROJA-1 sprints are not treated as valid because they no longer point to Project A. No errors are thrown in the logs.

Workaround
No workaround at the moment, please engage support if this issue is observed.