JIRA wild-card text search not working

Curtis Egner October 5, 2016
 

4 answers

1 vote
David Skreiner
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 Leaders.
October 5, 2016

If I understand this right, there was a bug in Lucene that was fixed recently, and may result in the wildcard dropping from the query. The page lists a workaround.

https://confluence.atlassian.com/jirakb/wildcard-searches-using-phrases-syntax-does-return-results-741739415.html

https://jira.atlassian.com/browse/JRA-43405

 

 

 

Curtis Egner October 6, 2016

Thanks for the info. However, this bug seems to only apply to wildcards within phrases, with the workaround being to split into individual terms. My search is already using individual terms, not a phrase.

0 votes
Curtis Egner October 25, 2016

I am using version 6.4.12. I agree that it has something to do with special characters. I've encountered similar problems with periods that separate hierarchical names.

0 votes
Kevin Mote
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 Leaders.
October 25, 2016

I'm encountering the same problem. Did something recently break? What version of JIRA are you using? (I'm running JIRA 7.0.2)

UPDATE: I just noticed that my wildcard searches are only broken on hyphenated words. They work fine on words that have no hyphens. I wonder if the underscores in your words are what is causing your problem. I have submitted a bug report (https://support.atlassian.com/servicedesk/agent/GHS/issue/GHS-59251).

0 votes
Curtis Egner October 5, 2016

I want to use an Advanced Search such as the following:  text ~ "filename_*.h" 

I expect this to find any issues that mention the source files:  filename_1.h, filename_2.h, filename_3.h, etc. However, this is not working. I can change the * to a 1, 2, or 3 and find issues, but any variation of the wild-card version I've tried does not return any results.

Any ideas why this doesn't work?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events