-
Bug
-
Resolution: Won't Fix
-
Low
-
Severity 3 - Minor
-
NOTE: This bug report is for JIRA Cloud. Using JIRA Server? See the corresponding bug report.
Summary
The options of custom fields that were disabled are returned via REST request. Affected custom fields include:
- Select List (single choice)
- Select List (multiple choices)
- Select List (cascading)
Steps to Reproduce
- Configure a custom field of any of the affected type listed above
- Add multiple options
- Disable one option and verify that it is not shown in the screens
- Run the following REST request
GET /rest/api/2/issue/createmeta?expand=projects.issuetypes.fields
- Monitor the custom field options returned
Expected Results
Only non-disabled entries should be returned in allowedValues
Actual Results
All the custom field options are returned in allowedValues json array
Notes
Similar request from Atlassian Answers: https://answers.atlassian.com/questions/274145/hidden-options-for-custom-fields-via-rest-api
Workaround
No workaround is available as of now
- is related to
-
JRASERVER-61594 disabled customFieldOption entries returned in allowedValues in GET issue/createmeta Rest Api
- Gathering Impact
- relates to
-
JRACLOUD-84798 Disabled custom field options should not be returned as allowed values when doing GET requests
- Gathering Interest