We couldn't export Custom Field Default Value XXX. Reason: java.lang.Exception: This export context type does not support project (CrossProjectDataExportContext). [JCMA 000]

Issue Summary

This is reproducible on DataCenter: Yes

Steps to Reproduce

1. Create a custom field of type VersionPicker/Project Version with the default value.
2. Reference this custom field in CPD Data (like AR plans, Assigned To Me Gadget)
3. Migrate the plan.

       For point 2 - 

       Scenario-1

1. Create a dashboard
2. Create a custom field of type project version.
3. Create a project (say ABC)
4. Add default value for custom field project version as ABC
5. Add any gadget referencing the custom field example `Assigned To Me` to the above dashboard.
6. Add the above custom field to the gadget.
7. Enable the DF com.atlassian.jira.migration.dashboard-migration.feature
8. Migrate the plan by selecting at least one project.

Expected Results

This export error should not occur in the data preparation preflight check.

Actual Results

The below exception is thrown in the CROSS_PROJECT_DATA.log file:

Error "2024-03-07 08:03:36.972439 ERROR CROSS-PROJECT-DATA project-export We couldn't export Custom Field Default Value 'XXX'. Reason: java.lang.Exception: This export context type does not support project (CrossProjectDataExportContext). [JCMA 000]" 

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available.