The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Why does JQL LIKE (~) operator not find my issue?

Scott Evans
Contributor
October 17, 2013

Today I was trying to query some customer issues in JIRA using a text custom field “SF_case” field and noticed an inconsistency.

Running the following query returned nothing but saying “No matching issues found.” (NO error was reported):

% SF_case ~ 00002075

I got the expected result only when the number was enclosed by either single or double quotes:

% SF_case ~ '00002075'

% SF_case ~ "00002075"

Note that in case of another custom field, all three queries below work as expected:

% GlobalID ~ 64412

% GlobalID ~ '64412'

% GlobalID ~ "64412"

If the same “~” operator is used for both fields, then why their behavior is different?

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
John Bishop
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
October 17, 2013

Is GlobalID the same text custom field type? Are the using the same type of searcher?

Perhaps it is because of the leading zeros in the SF_case value. Without the quotes, Jira might be interpreting the value as 2075 instead of 00002075.

Scott Evans
Contributor
October 22, 2013

Yes they are using the same searcher and are the same text field type.

TAGS
AUG Leaders

Atlassian Community Events