JIRA JQL - autocomplete for cascading select lists

Couldn'1 find an answer to this one and the closest I've seen is this one:


Could you please confirm, that the autocomplete function is not working with cascading select lists? You'd have to manually search by entering the right values, right?

customfield_11111 in cascadeOption("1st Level","2nd Level")

Cheers Christian

2 answers

1 accepted

0 votes
Accepted answer

Even if you don't use a function, then cascading select cannot auto-complete as of JIRA 6.0 and below.


customfield_11111 = "2nd Level"

I just found this myself today, and I am in the middle of trying to fix this for v6.1

What is the JRA issue number?

I actually did the work on an internal JIRA server, but now I copied the issue over so customers can find it.


(fixed in v6.1)

Hi, is this broken again in 6.1.3? It doesn't work for us.

Should clarify: it is currently impossible to do autocomplete on any JQL function including cascadeOption()

What I implemented is for "normal" JQL clauses for cascading select.

So, if you have a cascading CF called "Theme" you can type:

theme = Arch

and JIRA will autocomplete to (say)

theme = Architecture
but it will not be able to autocomplete
theme in cascadeOption(Arch
Was this your problem?

Thanks for the fast reponse Mark. We have a cascading CF "Required By" where parent option is a global region (Australia, Italy, etc) and child option is a customer.

In 6.1.3, if I try:

"Required By" = Aus

it does not autocomplete. Similarly at customer level:

"Required By" = "Atlass

(third quote intended) does not autocomplete.

Hmmm ... so I tested on JIRA 6.1.3 and it worked fine ... even with a space in the name.

Just to try to break it, I added a second CF with the same name as the first, and it was only showing me the values from the first field.
Furthermore, when I renamed the first field, it seemed to get even more confused (looks like the autocomplete details are in a stale cache ?).

Does this maybe sound like what happened to you?
If it is caching related, then a JIRA restart may help as a workaround ... ?
(But furst make sure the field names are unique)

This looks like a bug and my guess is that it is not specific to cascading select, but a probelm in auto-complete in general. Needs more testing, and I don't have any more time today.

In the meantime, I have raised https://jira.atlassian.com/browse/JRA-36058 but it would be good to do more investigation.
Please feel free to add more details to above bug report.

Thanks for bringing this to our attention.


I found this to be true. In above documentation it states: "auto-complete is supported for Custom Fields of type picker, group picker, select (except 'Cascading Select'), check-box and radio button fields."

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

808 views 3 9
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you