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.  

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.

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"

Still not fixed for cloud despite the corresponding suggestion saying it has been ... 

Same issue here. Can we please get rid of the 'None' option for Cloud?

I have the same issue - I have required fields (done through fields configuration) and I still see NONE option. System doesn't allow you to continue with 'none' but this is quire annoyiung

This should be re-opened. "None" is no longer removable, even if making it a required field and adding a default value. I'm now having to create additional validators to make sure my users aren't submitting "None" in my required field. v7.7.1

Any plans to fix this in Cloud version?

This is still not fixed for Jira Cloud.

In Jira 7.8.1, having the issue.

I found that the following mitigated my problem:

sed - 's/#velocimacro.library.autoreload/velocimacro.library.autoreload/' /opt/atlassian/jira/atlassian-jira/WEB-INF/classes/velocity.properties

sed -i 's/\$i18n.getText("common.words.none")/--\ Please\ Select\ --/g' /opt/atlassian/jira/atlassian-jira/WEB-INF/classes/templates/plugins/fields/edit/edit-select.vm

reboot

I am using Jira 7.5.1,  created a new, required, custom field with a default and the NONE option is showing up for me too. 

I am using Jira 7.7.1, created a new, required, custom field with a default and the NONE option is showing up for me too. 

Hi ben.herron2, we've created a ticket on behalf to investigate further on this. You should receive the notification shortly.

This is literally still not fixed in 7.x 

What the hell Atlassian?

How can I accomplish this if:

• I am on JIRA Cloud
• I do not want the field to be set as "Required" 

The inability to just simply remove "None" is shocking. JIRA is supposed to be a flagship product, and this is absolutely unacceptable.

I'm going to test this in OnDemand before asking a question.

It would be nice , if whenever this gets worked on, if the solution is.... to be able to deactivate the display of "None" at the field configuration level for Select fields.
By having something like a checkbox option of 'display'/'not display' the "None" option could then be customised to individual fields. As sometimes it makes sense to have the "None" option available even if a default is.
(and be backward compatible with existing Select field types)
adding my vote for this to get to the work list.

Seven years this problem has been outstanding; Nov 2005 to Nov 2012 and no one from Atlassian will fix it in all of this time. And now we have to wait another year? What lousy customer service.

No one likes these unwanted NONE options appearing everywhere. Each time I upgrade our company's Jira system I have to re-customize all of the velocity files. I'm not a developer and I've only been able to successfully remove none from a few of the custom fields. You can't make everything required and that solution doesn't work most of the time anyway.

Just like the severity vs. priority controversy, Atlassian does not listen to its customers or adhere to industry methodology. Keep raising those license costs though!

A little disappointed that this won't be addressed in the next 12 months.

Fabian, you've completely missed my point. There are other priorities. Age is irrelevant. Inconsistent behaviour is a bit more relevant. Other priorities are more important. I'm not sure how else to put it.

Nic, I second your opinion when talking about feature requests, but this is imho not true for no-brainer improvements. Other feature requests, the votes, and relative ages do not justify that such things do not get the attention they need. This is especially true when an inconsistent behavior (between different OOTB custom field types) was introduced that should not exist. 170+ votes 16+ support requests concerning this issue and a solution on the silver plate... what are you waiting seven years for

Fabian, have a quick look at the list of outstanding feature requests, the votes, and relative ages. "But why hasn't the one that affects me a lot been fixed" is a common refrain, but there are good reasons. Mostly down to "it's not as popular/important/relevant to other people". This one is a nice-to-have in my book, I've voted etc. There's at least 20 other things I'd want Atlassian to fix/improve first. Age of issue is almost completely irrelevant to be frank,

Created 19/Aug/05 2:12 PM ??? doh

This seems like a no brainer to me. It already works for radio buttons (required + default value). Why are you making this so painful for you users?

If custom field that is a set of radio buttons is required and has a default value associated with it, "none" shouldn't be an option, nor should any existing issue match "is empty" on the custom field. All issues should have their value set to the default unless and until otherwise actively changed.

It may make more sense to have this as an optional value or some form of tuneable configuration. When this field is not required, the option to select NONE is valid and will match the JQL for EMPTY. But when this field is required, there may be a case for the NONE but you'll never have a valid record for the JQL of EMPTY.

I guess it comes down to this: If it is Required then None has to be Specified. If it is not Required then None is provided by default and will match EMPTY. This is something that has to be figured out at the screen rendering level, which probably won't be impossible since that's where validations are too.

What about having a configuration option to include or to exclude the none Value? Since JRA-3666 was the cause of this issue, simply deleting in all cases the none option it will reopen JRA-3666. A configurable option for all related custom fields (select list, radio buttons, any future other options) will solve both problems.

+1 please fix.

Please resolve this. I mean you can't ignore an issue that's been around for ages... Cheers Christian

When you will fix this? It's not possible that this is so hard to fix.

Please fix this - it is too confusing for users and frustrating for admins to have to deal with this issue. (OnDemand user)

Was this fixed in the OnDemand service? Suddenly the "None" option is missing from my radio fields.

Could this issue please be assigned and fixed?

Very Sad. This item is open for almost 7 years now and JIRA Studio on-demand users like us have no workaround too.

This seems like a simple request, can we at least get it on the roadmap?

+1 vote, we are getting number of requests to delete 'None' option from select list

With the None option always showing, it's basically not possible to created Required fields.

The last update I see from Atlassian Personnel is more than 2 years ago. Do we have an idea on when or if this is going to be addressed?

The work arounds suggested are problematic and create maintenance issues. The problem of None in a select list should be addressed immediately. You might want to consider that there are many other products of this type in the market that have resolved this type of issue years ago.

We would very much like to see this fixed as soon as possible - 5+ years (and counting) seems an awful long time to have an issue like this opened up

Please for the love of god fix this. It's super annoying.

None should never be used for a non-selected value. The standard that you see in almost all UIs is -- Select --, or something similar, to inform the user that they need to make a selection.

I would suggest adding a new i18n value, that is not the general common.words.none, but the i18n files are harder to change than a VM file, so not really worth it.

Added my vote. This seems like it should be low hanging fruit. Please fix this.

Added my vote to this issue.

Another vote for this issue. I'm using JIRA v4.2.2

Thanks for your work and time.

we are running 4.2.1

"None" is showing up in a field where "None" was never configured in

This is very frustrating for us, when we just need a Yes No field. Event radio buttons force a "none" option.

The single-select custom field needs to be configurable enough to support all possibilities here. How can this not be fixed after five years?

+1 - Please make this change.

+1 This is very important.

"None" should never be added by Jira. Instead, there should always be one item marked as default for this field type. The UI for creating and editing this field type should enforce that. A default is always needed for two reasons: to determine which value to display initially in a dropdown for the field when the value has not been set yet, and to provide a value for the field when a new issue is created from a source that does not set a value for the field (e.g. from email, or from a screen that does not include the field).

The workaround helped me succesfully to remove the 'None' option of the select list. I personally use the 'Please select' option which have no value to make the difference with the other values I insert in.

NB : I made these changes in my own velocity file and not in Jira's as shown, because the cascading select I use is mine, and implements/overrides Jira's.

Best regards
Nicolas