Issue Summary

When migrating Jira from Server/DC to Cloud, and using the Confluence Cloud Migration Assistant, the empty custom field configuration will not get mapped to their issue layout in the cloud.

Steps to Reproduce

Jira v9.8 and older

1. Install the latest JCMA
2. Create a project and ensure the screen uses custom fields
3. Create an issue for the project where the custom field value is empty
4. Create an issue for the project where the custom field value is not empty
5. Migrate the project to the cloud

Jira v9.9 and newer

1. Install the latest JCMA
2. Create a project and ensure the screen uses custom fields A and B
3. Modify the Empty custom field configuration and allow the custom field A to be hidden when empty, and custom field B to be displayed when empty
4. Create an issue for the project where the custom fields A and B's values are empty
5. Create an issue for the project where the custom fields A and B's values are not empty
6. Migrate the project to the cloud

Expected Results

• Jira Cloud will behave consistently with the Jira DC and empty fields will be hidden

Actual Results

• Empty fields are displayed in Jira Cloud by default, as opposed to Jira DC, where empty fields are hidden by default
• JCMA does not cause issue layouts on the migrated projects to be created in a way that they behave consistently with the source Jira DC

Jira v9.8 and older

• Issue layouts for the migrated projects don't have the custom fields in the "hidden when empty" state

Jira v9.9 and newer

• Empty custom field configuration preferences are not translated into issue layouts in the cloud

  Platform	Field A (when empty)	Field B (when empty)	Comments
  Jira Cloud	Displayed	Displayed	The Issue Layout was not created to match Jira DC's Empty Custom Field Configuration
  Jira DC	Hidden	Displayed	Expected behavior as configured in the Empty Custom Field Configuration

Workaround

• Modify each issue layout for the migrated projects and move the desired fields under the Hide when empty divider