JQL search not working

[Beth Seitz]

I have a saved JQL search to find issues that need assignment. But when I run the search, it often returns results that blatantly contradict the filters.

JQL: 

status in (Done, "In UAT") AND "Doc Team review[Dropdown]" = Needed AND "Doc Owner[User Picker (single user)]" = EMPTY ORDER BY fixVersion ASC, cf[10009] DESC, project ASC, created DESC

First result in the list: 

status = Done, which is correct

Doc Team review = Completed, which is wrong - should only find Needed

Doc Owner = (a specific user), which is wrong - should only find Empty

[Walter Buggenhout _ACA IT_ · Accepted solution]

Hi @Beth Seitz and welcome to the Community!

I cannot see anything wrong with the query you shared there, but it does seem your search results are not consistent.

Getting inconsistent search results usually indicates a problem with your Jira instance's index. Reindexing should happen automatically in cloud and you cannot trigger a reindex yourself as a user.

If this behaviour continues, you may want to reach out to Atlassian support and have them look directly into your site.

Hope this helps!

[Jack Brickey]

Hi @Beth Seitz , Welcome to the community.

One thing I would note is that you should use "is Empty" rather than "= Empty". However, that doesn't necessarily explain all of what you were experiencing. What I would like to suggest is let's break this down into simple components and test that first period having done that week and then reassemble it into a single JQL. Can you try the following and see what your results are?

• "Doc Team review[Dropdown]" = Needed
  
  "Doc Owner[User Picker (single user)]" IS EMPTY
  

Hopefully we can get the results of those to JQL's to perform the way that you expect.

[Beth Seitz]

Thanks, had trouble finding the right syntax for empty. That gives me the same results.

I did notice that, in bookmarking the search, the bookmarked URL includes a Jira issue ID in it. I wonder if in running it from that bookmark, Jira is trying to include that named issue, and then returning something random in its place. It does seem to be just the first result in the list that often shouldn't be included at all.

Of course it also makes it fun to test, that I need to triage these issues out, so the queue is often empty.

[Jack Brickey]

While there may be some recent bug introduced that would explain things, that would not be my first suspicion. Did you try the single JQL statements I suggested?

[Beth Seitz]

Yeah, they work fine. Likewise if I edit the JQL and hit Search it seems to work fine. It's running from the bookmark where I get weird stuff. (Although now there are no issues that meet the full list of criteria, so I get the expected 'no search results'.)

[Jack Brickey]

I would ignore the bookmark for now. Does the full JQL work if entered as below? 

status in (Done, "In UAT") AND "Doc Team review[Dropdown]" = Needed AND "Doc Owner[User Picker (single user)]" is EMPTY

[Beth Seitz]

Sort of -- there are no search results now (as expected). (This is a triage search, so the issues fall out of it once assigned.)