Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
7.13.18, 8.13.1, 8.13.5, 8.16.1, 8.20.0, 9.4.0, 9.12.0, 9.14.0
-
None
-
7.13
-
2
-
Severity 3 - Minor
-
2
-
Description
Issue Summary
It is possible to create an issue with a disabled value on a custom field, by setting the value directly on the URL.
Steps to Reproduce
- Create a custom field of type Select list (single choice).
- Add two values to the custom field, where one is going to be disabled.
- Add the custom field to the Create Screen.
- Create a URL for the Create Issue screen, such as: https://<JIRA_URL>/secure/CreateIssueDetails!init.jspa?pid=10043&issuetype=14&customfield_10121=12140
- The id 12140 is the disabled value.
- The issue will be created with the disabled value.
- Once you edit the custom field's value, the disabled one no longer appears in the drop-down list.
Expected Results
It should not be possible to populate custom fields with disabled values.
Actual Results
The Issue is created with a disabled value on the custom field.
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available
Attachments
Issue Links
- relates to
-
CONFSERVER-95249 Confluence allows choosing a disabled custom field value on the create new issue UI from Jira Issues Macro
- Closed
-
BSERV-19369 Bitbucket allows choosing a disabled custom field value on the create Jira issue UI
- Long Term Backlog