Issue Summary

When migrating Jira projects using Cloud-to-Cloud migration with the plan selection option set to REFERENCED ("jiraPlanSelection": "REFERENCED"), Advanced Roadmaps plans whose issue sources rely on nested/indirect saved filters (e.g., filter = filter1) are not identified as being associated with the project in scope. As a result, the project and the base filter migrate, but the Plan itself is skipped during export/import.

Steps to Reproduce

1. Create Project A.
2. Create Filter 1 with JQL: project = "Project A".
3. Create Filter 2 with nested JQL: filter = "Filter 1".
4. Create an Advanced Roadmaps plan (Plan 1) and set its issue source to Filter 2.
5. Initiate a Cloud-to-Cloud migration for Project A with "jiraPlanSelection": "REFERENCED".

Expected Results

The migration engine resolves the nested filter hierarchy, identifies that Plan 1 references Project A, and migrates Plan 1 along with the project and filters to the destination site.

Actual Results 

Project A and Filter 1 migrate successfully.

Plan 1 is not detected as referencing Project A and is excluded from the migration.

Workaround

1. Direct Filter / Project Assignment: Update the plan’s issue source in the source instance to reference the project directly (or use a direct non-nested filter such as project = ProjectA), then run the migration.
2. Migrate All Plans: Configure the migration plan with the option to migrate All Plans rather than only referenced plans.