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

Strange JQL behaviour when summary contains a number

bschmi

Hi Community,

I created two issues.

The first one's summary reads:

Update myhost.example.org, 07.02.2020

The second one's summary reads:

Update myhost.1example.org, 07.02.2020

Unintentionally I queried via JQL as follows:
summary ~ "myhost.example.org,07.02.2020"
Notice the missing blank space between the comma and the date (07.02.2020).

To my surprise Issue Navigator showed my a result anyway!

I got curious and tried to query the second one by:
summary ~ "myhost.1example.org,07.02.2020"
Again, notice the missing blank space.

In this case I do not get any result. I tracked it down to the "1" in the domain (1example.org).

Although I fully understand that it is really crucial to have a correct specified JQL query here - why does one query do not consider the missing blank space but for the case there is a number in the domain it cares?

Thanks,
Birgit

Accepted answers

Ignacio Pulgar

Hi @bschmi

Blankspaces are not stored at all in the Lucene index, so they cannot be considered in any ways.

Too common words, like prepositions, are not stored in the index either.

Combinations of letters plus numbers is known to cause issues:

https://jira.atlassian.com/browse/JRASERVER-31882

Just for curiosity, does this search work?

summary ~ "myhost.?example.org,07.02.2020

And this one?

summary ~ "myhost.*example.org,07.02.2020"

Hope it helps.

All comments

Jack Brickey

While I do find it odd that nothing is found in the second case, it is important to note that you are using the ‘approximate’ operator here “~”. That operator is not looking for exact match so spaces could be ignored.

Ignacio Pulgar

Hi @bschmi

Blankspaces are not stored at all in the Lucene index, so they cannot be considered in any ways.

Too common words, like prepositions, are not stored in the index either.

Combinations of letters plus numbers is known to cause issues:

https://jira.atlassian.com/browse/JRASERVER-31882

Just for curiosity, does this search work?

summary ~ "myhost.?example.org,07.02.2020

And this one?

summary ~ "myhost.*example.org,07.02.2020"

Hope it helps.

bschmi

Hi @Ignacio Pulgar

Neither summary ~ "myhost.?example.org,07.02.2020" (I took the liberty to add a " at the very end) nor summary ~ "myhost.*example.org,07.02.2020" produces any output.

JRASERVER-31882 was an interesting read.

Thanks also to @Jack Brickey for your contribution.

Cheers,
Birgit

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server

jql