-
Suggestion
-
Resolution: Fixed
-
16
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? 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
-
JRASERVER-31129 Better handling of "none" option in custom field drop-downs during issue update.
-
- Gathering Impact
-
- is caused by
-
-
- Closed
-
- is related to
-
-
- Closed
-
-
- Closed
-
- Gathering Interest
-
- Gathering Interest
-
JRADEV-17412 Loading...
- relates to
-
- Closed
-
- Gathering Interest
-
- Gathering Interest
- supersedes
-
- Closed
- mentioned in
-
-
-
-
-
-
[JRASERVER-7687] Remove 'None' option if select list is required and has a default selected
| Remote Link | New: This issue links to "Page (Confluence)" [ 722438 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 722437 ] |
| Workflow | Original: JAC Suggestion Workflow [ 3062484 ] | New: JAC Suggestion Workflow 3 [ 3693948 ] |
| Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
This is not a solution.
The whole point of a required field is forcing the user to fill in a value and not just leave it with the default NULL. By creating a custom option (called "Please select.." for example) and setting it as default, the user still can ignrore those "required" fields and create the issue without touching them, making the "required" state meaningless.
I need to force users to actually fill the field with a value that is not NULL, and I need the option to rename the default NULL state to something other than "none".
To quote Jeremy Clarkson: How hard can it be?
@Mao Lee: You probably didn't set a default value. In this case "None" still appears, since it's Jira's "default" default value for custom fields. Change it to one of the values you specified and you should be good.
I'm still seeing 'none' as an option in the drop down even though I set the field to "Required" and set the default fields
Workaround for this issue:
To remove the field, edit atlassian-jira/WEB-INF/classes/templates/plugins/fields/edit/edit-select.vm.
Delete the following lines in edit.select.vm class file:
...
#if (!$fieldLayoutItem || $fieldLayoutItem.required == false
<option value="-1">$i18n.getText("common.words.none")</option>
#else
<option value="">$i18n.getText("common.words.none")</option>
#end
...
The following code should remain:
...
<select name="$customField.id" id="$customField.id"> #foreach ($option in $configs.options)
<option value="$textutils.htmlEncode($option.value)"
#if ($value && $value == $option.value)selected#end
>$option.value</option>
#end
</select>
...
This does not work for cascading select field. When I select parent ... child field is still has "NONE"
| Workflow | Original: Confluence Workflow - Public Facing v4 [ 2600082 ] | New: JAC Suggestion Workflow [ 3062484 ] |
I use cloud version and I see None option even after setting a selection list (cascading type) as required & default value to one of the specified value.