The option for field does not exist, when it clearly does

[Ancau_ Adelina]

I have a field named Drop that I'm using in my data analysis and I use JQL to filter its values. When I want to filter the value "none", i get the error The option 'none' for field 'Drop' does not exist.

This was also reported here but the workaround found by the reporter doesn't work in my case.

[Albert López]

In my case, what I found is that we have two custom fields that have the same name, only changing a letter in capital words.

So, for the query, you can use as cf[XXXX] (for example, cf[25000] = "VALUEX") and the query will work normally.

[Manon Soubies-Camy]

Hi @Ancau_ Adelina and welcome to Community!

Can you try using the autocomplete when typing your JQL? What is suggested when you type the following:

 "Drop" =

Can you also try with the below JQL?

"Drop" is empty

[Ancau_ Adelina]

Autocomplete suggests other valid options, but not "none".

Using "Drop" is empty gives me the tickets that don't have the Drop field.

[Manon Soubies-Camy]

Another possibility could be that the value "none" is actually "none " with a space at the end or something like that. What type of custom field is Drop? Is it a dropdown, a cascading select list, a text field?

[Dirk Ronsmans]

Maybe even an Insight custom field? :)

if you can I’d check the configuration of the field. Making sure that the context of that value is actually valid for what you are searching too ..

if you can screenshot the config even better :)

[Ancau_ Adelina]

@Manon Soubies-CamyI've tried adding spaces but I still get the error.

Drop is a dropdown.

Apparently "none" is actually "none (not available)" and there is also a "None" option. However these can't be accessed through the JQL either.

[Ancau_ Adelina]

@Dirk RonsmansI think this is the field configuration.

The other (valid) values for the Drop field contain letters, numbers and even symbols (dots and dashes), so I don't think type mismatch could be an issue.

[Manon Soubies-Camy]

Hi @Ancau_ Adelina, does it work if you remove the "project = xxx AND" from your JQL query?

@Dirk Ronsmans may be right when talking about the field context. Maybe this value "none" is not available in that project.

[Ancau_ Adelina]

@Manon Soubies-Camyit doesn't work if i remove "project = xxx AND".

I don't know how the value could be not available in the project, since I can clearly see tickets having it.

[Dirk Ronsmans]

Hey @Ancau_ Adelina ,

Is it actually "none" in the configuration? Cause in Jira in a lot of things when something (like a single select field) has the value "None" it's actually an empty field.

You could try "Drop" IS EMPTY and see if that works?

[Ancau_ Adelina]

I'm not sure about the configuration but for "none" it is definitely not an empty field. When I use "Drop" IS EMPTY I get the ones that don't have the Drop field, not the ones that have "none" as value of the Drop field.

[Dirk Ronsmans]

i'm going with my next gut feeling here, any chance you have multiple fields with the name "Drop"? 

[Ancau_ Adelina]

No, just this one.

[Deleted user]

I do not know if you are still looking for an answer on this one @Ancau_ Adelina

However, it has happened to me in the past that the filter would not work when I was using (") for the value and once I change to (') it would. So might worth giving it a go like that (= 'none')