nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Why is JQL Auto-Complete not listing options for one Custom Field?

Mark Symons

My JIRA v6.3.4 uses multiple custom fields of type checkboxes, all with search template "Multi Select Searcher". For all but one of these fields, JQL Auto-Complete is working fine. However, the most recently added field is not auto-completing.

Thus, I can perform a query based on "customfield1 AND customfield2", and as I type, I get auto-complete working great for customfield1.... and nothing whatsoever for the (new) customfield2.

I have checked and the answer is not in the KB article JQL Auto Complete is no longer working for individual users.

Any thoughts? It's quite important that Auto-Complete should work for this field or it becomes far less useful.

I am happy to work with the (MySQL) database if that would help me investigate the problem and solve it.

Accepted answers

Mark Symons

Sigh... I have fixed the problem. Auto-Complete is now working well.

All I had to do was tweak the configuration of the custom field and change the applicable issue type from a sub-set of issue types to "All Issue Types".

I am delighted that all the options now list... it makes such a huge difference to usability. Still, it does seem to me that JIRA should not have behaved this way.

All comments

Jobin Kuruvilla [Adaptavist]

First thing to check is whether the field has a searcher associated with it or not. If it has one, then check if the field is available in the context of your search (for the project and issuetype selected).

Mark Symons

Thanks for the speedy response, Jobin. Checking the customfield table, CUSTOMFIELDSEARCHERKEY = com.atlassian.jira.plugin.system.customfieldtypes:multiselectsearcher This matches the config as seen in UI, and reported in original question. I did neglect to mention that JIRA has been re-indexed multiple times since the problem custom field was added. Both "Background re-index" and "Lock JIRA and rebuild index". The auto-complete never works. Either when typing a simple global query: "My Custom Field" = ...or a more specific: Project = "My Project" AND issuetype = Defect AND "My Custom Field" = The problem is only with Auto-Complete. If I specify the options (that are failing to display automatically) then the JQL search works just great. Examples: "My Custom Field" = option1 "My Custom Field" in (option2,option3)

Jobin Kuruvilla [Adaptavist]

Ah ok. Any error in the logs when you trying the auto complete?

Mark Symons

There are no errors in the logs, examining acces log, plus atlassian-jira.log and catalina.out. I have just used Firebug plugin to examine what is being returned from the JIRA server. The response is HTTP 200, and the JSON content is: {"results":[]} By the way, I have not yet logged a Support Call with Atlassian... preferring to try here first.

Mark Symons

I am delighted that all the options now list... it makes such a huge difference to usability. Still, it does seem to me that JIRA should not have behaved this way.

Rick Trudeau

Hi Mark, You've run into the bug described at https://jira.atlassian.com/browse/JRA-35126 Please go vote for it! I get hit by this bug all the time and it's beyond me why its considered Minor given that it completely breaks auto-complete.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-administration

jql