Issue Summary

During a Jira Cloud-to-Cloud migration, the custom field configuration (Required/Optional) is not migrated as part of the field configuration settings.
This means that after migration, the custom field is set to Optional regardless of being Required on the source site.

Note: This discrepancy is not explicitly called out in the What migrates in a cloud-to-cloud migration for Jira article.

Steps to Reproduce

1. Create a new custom field
2. Associate the custom field with a project
3. Modify the field configuration and change the custom field to Required
4. Migrate the project using the Jira C2C Beta Tool
5. Observe the custom field configuration in the destination site

Expected Results

The field configuration settings are migrated and the custom field is listed as Required

Actual Results

The field configuration settings are not migrated and the custom field is listed as Optional

Workaround

1. Manually modify the field configuration after migration and change the custom field to Required.
   OR
2. Update modify the field configuration via an API call: The Jira Cloud platform REST API - Update field configuration items
   1. Example of an API call to set a custom field as Required in the field configuration settings:

      curl --request PUT \
        --url 'https://<your site>.atlassian.net/rest/api/3/fieldconfiguration/<field configuration ID>/fields' \
        --user '<user:API token>' \
        --header 'Accept: application/json' \
        --header 'Content-Type: application/json' \
        --data '{
        "fieldConfigurationItems": [
          {
            "id": "customfield_<custom field ID>",
            "isRequired": true
          }
        ]
      }'