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; } } }

textfields ~ "fraudlink" OR textfields ~ "neptune" - No results

Stephen Call_swvhch

Any assistance with the following query would be greatly appreciated!

When I search for textfields ~ "fraudlink*"

I get 2 hits.

When I search textfields ~ "neptune*"

I get 454 hits.

So when I search for the OR of those: textfields ~ "fraudlink*" OR textfields ~ "neptune*"

I should get between 454 and 456 hits.

But I get 0!

Parentheses don’t help.

Accepted answers

Sergei Troshin_usua2u

Hi @Stephen Call and Welcome to Atlassian Community!

It seems that textFields is broken. Have you tried using the text expression instead of textFields?

For example, you can use:

text ~ "fraudlink*" OR text ~ "neptune*"

The only difference between textFields and text is that text also searches through comments and worklogs.

Some theory

The text field:

The textField field:

See JQL fields

All comments

unknown

Hello @Stephen Call

JQL can sometimes be a bit counter intuitive if you're from a SQL world

Use textFields ~ ("fraudlink" OR "neptune")

David Friedrich

@[deleted]this JQL Statement will not work. Jira does not support OR inside a ~ clause. It can only handle a single search term at a time.

unknown

My mistake. Ignore what I said.

So, I tested the OP's original JQL myself doing a like comparison on the summary field:

summary ~ "test" found two issues that matched
summary ~ "deleted" found two issues that matched
summary ~ "test" OR summary ~ "deleted" found four issues that matched. The two from the first set and the two from the second set

The OR keyword seems to be working so far. Then I tried using the multi-character wildcard, like they did:

summary ~ "tes*" found two issues that matched
summary ~ "del*" found two issues that matched
summary ~ "tes*" OR summary ~ "del*" found four issues that matched. The two from the first set and the two from the second set

The wildcard and the OR keyword seem to be working fine. I then tried using textFields to broaden the scope:

textFields ~ "tes*" found 13 issues that matched
textFields ~ "del*" found two issues that matched
textFields ~ "tes*" OR textFields ~ "del*" found nothing! Eh?

I utilised the Parse JQL Query API endpoint with strict validation to test the JQL, and no errors were reported.

I have no idea at all why two joined textFields like searches fail

David Friedrich

The JQL you are using is correct.

textfields ~ "fraudlink*" OR textfields ~ "neptune*"

This SHOULD give you all issues having textfields with either fraudlink... or neptune... in them.
However, why it is returning 0 I can not say.
If the JQL is not showing any errors if you try it here: [YOURSITE]/issues/?jql=textfields%20~%20"fraudlink%2A"%20OR%20textfields%20~%20"neptune%2A"
it should work and produce the 456 results.

Sergei Troshin_usua2u

Hi @Stephen Call and Welcome to Atlassian Community!

It seems that textFields is broken. Have you tried using the text expression instead of textFields?

For example, you can use:

text ~ "fraudlink*" OR text ~ "neptune*"

The only difference between textFields and text is that text also searches through comments and worklogs.

Some theory

The text field:

The textField field:

See JQL fields

unknown

That's interesting. Because they are so broad in scope, I very rarely use text and textFields, so I've never encountered any of these problems.

Now, here's where it gets really weird... the problem only occurs when submitting the offending JQL in the GUI or using the newer Search for issues using JQL enhanced search API endpoint. Both of those returned no results

However, when I submitted the exact same JQL of textFields ~ "del*" OR textFields ~ "tes*" using the old Search for issues using JQL API endpoint, it worked as expected and return the full, correct set of matching issues.

I looked through JAC to see if this bug has been logged by anyone, but nothing so far. I might raise it over on the Developer's forum to see if anyone has seen this before.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud