Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to remove none option from Multi select list custom field?

Hello All,

How to remove None option from Multi select list custom field? 

I have made multi select field as required still it shows the None option.

Any help would be appreciated!

Thanks in Advance,


4 answers


Go to issues --> Custom Fields --> Select your field --> Configure --> Edit Default value.


Hi Victor,

I have done that still it shows the None option.



I have added below script in Behavior Initialiser and mapped to particular issue type. However default value shows for all issue type in the project

def desc = getFieldById("summary")

def defaultValue = """Default Value""".replaceAll(/ /, '')

if (getActionName() == "Create" && !underlyingIssue?.description) {

0 votes

The "none" option in multi select field is not a real value, it is used to indicate that you want to clear that field.

If you make the field required, users selecting none will be prompted that the input is invalid and they will have to make another selection.

If you really need to hide the none value, you could use behavior formField.setFieldOptions

I have a required field, but I can leave this field with "none" set on the second level. This is not a correct implementation of "Required"

Users are not prompted on the second level "None" entered !

I will call this a bug.

Cascading select field is a single entity. It's not 2 field.

From a data perspective, selecting a second-level value or not makes no difference... there is still data in the field.

In fact, there are some very valid business case for requiring a first-level value only.

I understand that the ability to have the "set required" functionality to be smart enough to give you this additional option whne the target field is a cascading select would be nice, but it would be a big change in the default implementation of the "set required" feature.

All that being said, using scriptrunner (and probably also some other apps) it is possible to apply validation to the cascading select to ensure that a second-level is always selected. Depending on your use case, this could be done with Behaviours, or Custom Validators in the workflow.

Is there an alternative way to achieve this, not using cascading 2 level lists?

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you