Issue Summary

The customer is experiencing an issue while attempting to create a new Jira Epic in Jira Align using the Jira connector. When trying to create an epic within the project "XYZ," a warning message is displayed in the Feature audit log, stating "400 Bad Request: customfield_xxxxx=<custom_fieldname> is required," and the Epic failed to be created in Jira.

However, if there is an existing Feature (Jira Epic) in Jira Align and I update its value, the synchronization between Jira and Jira Align is successful. Additionally, creating the Epic in Jira and adding my custom field also results in successful sync with Jira Align.

This is reproducible on Data Center: (yes)

Steps to Reproduce

1. Create a custom field of type (Select List single choice) in Jira and add the values
2. Create a custom field of type (CUSTOM FIELD SETUP - SELECT LIST) with the same name and same values in JA
3. In JA, map the new custom field under Field Management and map the respective values
4. Create a New JA Feature (Jira Epic) and wait for the sync

Expected Results

It's known the sync will fail if the Jira custom field is set as Required. However, the sync behavior should be consistent for both New and Existing Features (Jira Epics).

Actual Results

The sync only fails with the error message "400 Bad Request: customfield_xxxxx=<custom_fieldname> is required" when creating new features.

Workaround

As a workaround, if the custom field is set as optional in Jira, the sync works as expected.