-
Suggestion
-
Resolution: Unresolved
-
None
-
1
-
Issue Summary
When doing GET requests with endpoints such as /rest/api/2/jql/autocompletedata/suggestions?fieldName=[fieldname] disabled values are returned, what may cause issues with integrations (including Automation rules) considering that Jira won't be able to use it.
Steps to Reproduce
- Create a select type custom field, adding some possible options on it
- Disable one of the options (in /secure/admin/ConfigureCustomField!default.jspa?customFieldId=[fieldId])
- Try to access Get field auto complete suggestions
- All existing options are returned (disabled or not)
Expected Results
Only not-disabled option should be returned, or disabled options should be marked as not available.
Actual Results
All existing options are returned (disabled or not) as if they were all available to be used as field values, what may cause issues with integrations and/or with Automation rules.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- is related to
-
JRACLOUD-61594 disabled customFieldOption entries returned in allowedValues in GET issue/createmeta Rest Api
- Closed
-
JSWCLOUD-22931 Contextual dropdown - DISABLED options are still showing in the Automation
- Closed