-
Suggestion
-
Resolution: Unresolved
-
17
-
45
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
If you create a custom field that selects from a list, the "None" value will always be an option if it is not required.
Often, a custom field is only required on certain fields or transitions. While you can use a workflow validator to meet the requirement, it still shows "None" as an option.
- is related to
-
JRACLOUD-31129 Better handling of "none" option in custom field drop-downs during issue update.
- Closed
-
JRACLOUD-7687 Remove 'None' option if select list is required and has a default selected
- Closed
-
JRACLOUD-7320 Allow me to change the "None" in custom fields
- Gathering Interest
-
JRACLOUD-32463 Required "Select List (cascading)" custom field allows user to set child value to None if the field has a default value
- Gathering Interest
-
JRASERVER-42041 Allow removing "none" option for non-required Custom Fields, or allow required by screen
- Gathering Interest