-
Bug
-
Resolution: Won't Fix
-
Low
-
None
-
Severity 3 - Minor
-
NOTE: This bug report is for JIRA Cloud. Using JIRA Server? See the corresponding bug report.
- Create a drop-down custom-field with options A, B, and C.
- Create an issue and leave the value for the field as None.
- Edit the settings of the custom field and set default value to C.
- Edit the field config and set the field as required.
- View the issue you previously created - note that the field still has no value.
- Edit this field.
Actual: The drop-down is now set to A.
Expected: The drop-down should include the "none" value and have this set as its value. (it should fail on validation if the user does not set a value)
(This would be consistent with what happens on Create Issue when a CF is mandatory but has no default.)
- is caused by
-
JRACLOUD-7687 Remove 'None' option if select list is required and has a default selected
- Closed
- is related to
-
-
- Gathering Impact
-
- relates to
-
- Gathering Interest