Issue Summary

JSM automations on Jira Cloud lost the ability to set disabled options on select/multi-select custom fields. This is a regression from long-standing behavior that many customers rely on to hide options from end users while still allowing automations to populate those values programmatically.

Steps to Reproduce

1. Create a single-select or multi-select custom field on a Jira Cloud project.
2. Add multiple options to the field. Disable one or more options (so they are hidden from users in the UI).
3. Create a Jira Automation rule that sets the custom field to one of the disabled options (e.g., via "Edit issue" action).
4. Trigger the automation rule.

Expected Results

The automation successfully sets the custom field to the disabled option, as it has historically done. This allows admins to hide options from users while still using automations to populate those values when needed.

Actual Results

The automation fails to set the field value. The disabled option is not applied. The field either remains empty or the automation action silently fails/returns null for the disabled option.

Workaround

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