Issue Summary

When using Jira Automation to edit a custom field select list, a rule can assign a value to the list even if that value is disabled. This results in the disabled value being displayed and assigned to the field. Disabled values also appear when creating new rules, suggesting that edit issue does no check for a values "enabled" status at all.

This is reproducible on Data Center: yes

Steps to Reproduce

1. Set up a custom field select list with multiple options.
2. Add the custom field to all issues and issue screens in Jira.
3. Configure an automation rule that edits the field to add a specific option (e.g., Option A) when an issue is created.
4. Create an issue and verify that the option has been added to the select list.
5. Edit the field configuration to disable the previously added option (e.g., Option A).
6. Create a new issue and observe that the disabled option is not visible in the select list.
7. Check the created issue and confirm that the disabled option has been assigned to the field.

Expected Results

The rule will fail to assign a disabled value. The value is not present when creating a new rule that edits the custom field.

Actual Results

The disabled value will be added to the custom field, even though this is not possible via manually editing the rule. Creating new rules that edit the custom field still present the option to use disabled values.

Workaround

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