Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-19216

Wildcard search does not work if prefix is over 14 characters

XMLWordPrintable

      If I search for a summary using prefix-wildcard search and specify prefix larger than 14 characters, the result will be empty even if there are matching issues.

      Example:

      http://jira.atlassian.com/secure/IssueNavigator.jspa?component=10480&summary=true&pid=10240&type=2&reset=true&show=View+%26gt%3B%26gt%3B&query=%2BgetFieldsForCr*

      shows JRA-11597, which has "getFieldsForCreation()" in the summary. we search for "getFieldsForCr*", 14-character prefix + wildcard

      http://jira.atlassian.com/secure/IssueNavigator.jspa?component=10480&summary=true&pid=10240&type=2&reset=true&show=View+%26gt%3B%26gt%3B&query=%2BgetFieldsForCre*

      same request, with one letter added to the prefix - the result set is empty

            [JRASERVER-19216] Wildcard search does not work if prefix is over 14 characters

            Eric Dalgliesh added a comment -

            Thanks mdoar! I've sorted this issue out and removed the button.

            Eric Dalgliesh added a comment - Thanks mdoar ! I've sorted this issue out and removed the button.

            MattS added a comment -

            Oops, there was button marked Fixed on JDOG and I clicked it. I don't have permission to undo that status change. I suspect I was not supposed to have permission to make the original status change. That transition is probably missing a condition to check permission. Oddly enough this is exactly why I filed JRA-32601 earlier today. If an Atlassian admin can make this mistake, imagine how often JIRA admins do the same.

            MattS added a comment - Oops, there was button marked Fixed on JDOG and I clicked it. I don't have permission to undo that status change. I suspect I was not supposed to have permission to make the original status change. That transition is probably missing a condition to check permission. Oddly enough this is exactly why I filed JRA-32601 earlier today. If an Atlassian admin can make this mistake, imagine how often JIRA admins do the same.

            Guido Grune added a comment -

            Can reproduce the bug in 5.2.

            For us, the problem is high priority. Some of our user use the summary to categorize (starts with "FooBar-BarFoo-XY10") there issues and didn't find them.

            Guido Grune added a comment - Can reproduce the bug in 5.2. For us, the problem is high priority. Some of our user use the summary to categorize (starts with "FooBar-BarFoo-XY10") there issues and didn't find them.

            David Chan added a comment - - edited

            One sample method to reproduce (verified on 5.1.7):

            • Create a new issue with the description: myissue/foobar/ab12/fun
            • Do a search in issue navigator: 
              description ~ "myissue/foobar/ab12/fun"
              • Works as expected
            • Do another search, this time with a wildcard: 
              description ~ "myissue/foobar/ab?2/fun"
              • returns nothing
              • using * instead also returns nothing

            David Chan added a comment - - edited One sample method to reproduce (verified on 5.1.7): Create a new issue with the description: myissue/foobar/ab12/fun Do a search in issue navigator: description ~ "myissue/foobar/ab12/fun" Works as expected Do another search, this time with a wildcard: description ~ "myissue/foobar/ab?2/fun" returns nothing using * instead also returns nothing

            Eric Dalgliesh added a comment -

            I suspect the 14 characters thing is a red herring. I haven't done any investigation but my hypothesis is that this is caused by Lucene not matching against stemmed words. For example, "commenting" will get reduced to "comment" in the index, and the word "comment" does not match against the wildcard term "commenti*".

            Eric Dalgliesh added a comment - I suspect the 14 characters thing is a red herring. I haven't done any investigation but my hypothesis is that this is caused by Lucene not matching against stemmed words. For example, "commenting" will get reduced to "comment" in the index, and the word "comment" does not match against the wildcard term "commenti*".

            Gajan Umapathy added a comment - - edited

            Today I did a new search on JIRA 4.34:

            cf[10021] = IFC and comment ~ "SEHExcept*"
            it return 3 outputs.

            But the following ones don't return anything:
            cf[10021] = IFC and comment ~ "SEHExcepti*"
            cf[10021] = IFC and comment ~ "SEHExceptio*"
            cf[10021] = IFC and comment ~ "SEHException*"

            Instead the following one returns the 3 outputs as the first query:
            cf[10021] = IFC and comment ~ "SEHException"

            Gajan Umapathy added a comment - - edited Today I did a new search on JIRA 4.34: cf [10021] = IFC and comment ~ "SEHExcept*" it return 3 outputs. But the following ones don't return anything: cf [10021] = IFC and comment ~ "SEHExcepti*" cf [10021] = IFC and comment ~ "SEHExceptio*" cf [10021] = IFC and comment ~ "SEHException*" Instead the following one returns the 3 outputs as the first query: cf [10021] = IFC and comment ~ "SEHException"

            Nazia Tarannum added a comment -

            Atlassian

            Can anyone please help us..

            CONTAINS operator with wildcards (? *) is not working on Text Field type of Custom field .

            Query below does not returns any value:
            "Custom field name" ~ "WT-2.0.0-69-DHD-?" and project = WXYZ

            While query below returns the correct values
            "Custom field name" ~ "WT-2.0.0-69-DHD-1" and project = WXYZ

            Thanks a lot in advance!

            Let us know when this can be resolved? can it be resolved by JIRA 5.0 verison release. Let me know the tentative date atleast..

            Greatly appreciate your response.

            Thanks
            Nazia

            Nazia Tarannum added a comment - Atlassian Can anyone please help us.. CONTAINS operator with wildcards (? *) is not working on Text Field type of Custom field . Query below does not returns any value: "Custom field name" ~ "WT-2.0.0-69-DHD-?" and project = WXYZ While query below returns the correct values "Custom field name" ~ "WT-2.0.0-69-DHD-1" and project = WXYZ Thanks a lot in advance! Let us know when this can be resolved? can it be resolved by JIRA 5.0 verison release. Let me know the tentative date atleast.. Greatly appreciate your response. Thanks Nazia

              edalgliesh Eric Dalgliesh
              bbf762edcc79 Igor Sereda [ALM Works]
              Affected customers:
              9 This affects my team
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: