-
Suggestion
-
Resolution: Fixed
-
16
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Hi everyone,
Thanks so much for your votes and comments on this issue.
This issue has been resolved in our latest bug fix release for JIRA, JIRA 5.2.4. The 'None' option no longer appears when the select list is a required field and has a default value.
Thanks for your patience and we hope you appreciate our open approach to feature requests.
Cheers,
Bryan
JIRA Product Management
brollins at atlassian dot com
Original Description:
Due to fix implemented for JRA-3666 the 'None' option was added even when the field is required.
This makes sure that the user is forced to make a choice for the value instead of defaulting to the top of the list.
However if you have set a default value the 'None' option becomes irrelevant so should be removed.
- causes
-
JRACLOUD-31129 Better handling of "none" option in custom field drop-downs during issue update.
- Closed
- is related to
-
JRACLOUD-12773 Provide a custom field required without a "none" option on the resolve screen
- Closed
-
JRASERVER-7687 Remove 'None' option if select list is required and has a default selected
- Closed
-
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
- relates to
-
JRACLOUD-7320 Allow me to change the "None" in custom fields
- Gathering Interest
-
JRACLOUD-42041 Allow removing "none" option for non-required Custom Fields, or allow required by screen
- Gathering Interest
- supersedes
-
JRACLOUD-29009 Make remove 'None' from custom field to be configurable in jira-config.properties
- Closed