Disabled custom field options should not be returned as allowed values when doing GET requests

XMLWordPrintable

    • 2
    • 3

      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

      1. Create a select type custom field, adding some possible options on it
      2. Disable one of the options (in /secure/admin/ConfigureCustomField!default.jspa?customFieldId=[fieldId])
      3. Try to access Get field auto complete suggestions
      4. 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

            Assignee:
            Unassigned
            Reporter:
            Ilenice
            Votes:
            3 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: