• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Low Low
    • None
    • 4.16.1, 4.17.1, 5.4.2
    • Issue View

      Issue Summary

      Use of multi character wildcard % or * not returning expected results when used in the middle of the term in JQL search

      Steps to Reproduce

      For issues with the summary of Test ABC-ISSUE and TEST DE1-ISSUE:

      • query with Job *-ISSUE
      • query with Job %-ISSUE

      Similarly occurs when no dash is present after wildcard:
      For issues with the summary of Test ABCISSUE and Test DE1Issue:

      • query with Test *ISSUE
      • query with Test %ISSUE

      Expected Results

      For wildcard queries using * or % to return any result matching the rest of the query.
      In given instances to return all issues with the summary of Test ABC-ISSUE and TEST DE1-ISSUE, or with the summary of Test ABCISSUE and Test DE1Issue

      Actual Results

      For issues with the summary of Test ABC-ISSUE and TEST DE1-ISSUE:

      • using the search query of Job *-ISSUE returns no results
      • using Job %-ISSUE only returns the issues with Test ABC-ISSUE and not TEST DE1-ISSUE

      Similarly occurs when no dash is present after wildcard:
      For issues with the summary of Test ABCISSUE and Test DE1Issue:

      • using the search query of Test *ISSUE returns no results
      • using Test %ISSUE only returns the issues with Test ABC-ISSUE and not TEST DE1-ISSUE

      Other Examples:

      _ABC-FVG-003 _- Results with value ABC-FVG-003 as expected

      "ABC-NR1*" - Results in all values that begin with ABC-NR1* as expected

      "ABC-FVG*" - Does not return anything. Using "ABC?FVG*" or "ABC*FVG*" doesn't have any result.

      But "ABC FVG*" - Return's needed result. And variant "ABC FVG-*" works fine.

      Workaround

      Modify query to remove the characters after the wildcard: Test * returns all expected results

            [JSDSERVER-10852] Using wildcard * and % not returning expected results in JQL search

            Can we please see an increase in the priority of this from Low?  This bug is really blocking some usability for our search tools hitting Jira internally

            Benjamin Spead added a comment - Can we please see an increase in the priority of this from Low?  This bug is really blocking some usability for our search tools hitting Jira internally

            Jon Chandra added a comment - - edited

            Similar issue had been reported since 2005. https://jira.atlassian.com/browse/JRASERVER-6187.

            That one was closed with no resolution as far as I can tell

            Jon Chandra added a comment - - edited Similar issue had been reported since 2005. https://jira.atlassian.com/browse/JRASERVER-6187 . That one was closed with no resolution as far as I can tell

              Unassigned Unassigned
              ba8ad0b21fe9 Mateo
              Affected customers:
              10 This affects my team
              Watchers:
              15 Start watching this issue

                Created:
                Updated: