JIRA throws an error when searching for a saved filter.

XMLWordPrintable

    • 6.04
    • Severity 3 - Minor
    • Hide
      Atlassian Update – 28 May 2018

      Hi everyone,

      We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Time Out.

      Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.

      We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication.
      Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

      Thank you,
      Ignat Alexeyenko
      Jira Bugmaster

      Show
      Atlassian Update – 28 May 2018 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Time Out . Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Thank you, Ignat Alexeyenko Jira Bugmaster

      We have thousands of saved filters. When trying to search for an existing filter in a dashboard gadget or from the search for filters in the manage filters section we are getting an error for filters that exist with the following syntax.

      LPM (DOCSIS) - All

      It doesn't seem to like the parentheses in the name. We have many filters broken out like this. I am attaching a few screen shots form the manage filter search area. The first two error out (yes I tried to escape this as well.) The third returns 400+ results. It is even worse trying to find one in the dashboard gadget with the filter gadget.

      Summary

      • Using parantheses "()" in filter search seems to provide inaccurate result and throws error

      Environment

      • 6.4.7

      Steps to Reproduce

      1. Have several filter using variation of name "LPM (DOCSIS)","(DOCSIS) " ," (DOCSIS)"
      2. Go to Issues > Manage Filters > Search
      3. Perform the search by typing the filter name partially eg: "LPM (DO"
      4. Search the filter by typing the filter name fully "LPM (DOCSIS)"

      Expected Results

      • To be able to search through the filter

      Actual Results

      • Trying to search filter for "LPM (DOCSIS) - All"
      • If search the filter by typing the filter name partially eg: "LPM (DO"
        • Error is thrown " Could not parse the query text. Leading wildcards are not supported"
      • If search the filter by typing the filter name fully "LPM (DOCSIS)"
        • Will not get accurate search, will return result for (DOCSIS) related rather than the full LPM (DOCSIS) only

      Workaround

      • To search for LPM (DOCSIS), ensure parantheses is closed, for eg:
        • LPM (DO) instead of LPM (DO to avoid the error " Could not parse the query text. Leading wildcards are not supported" being thrown

      Notes

      • Seems like the search are concentrating to the value inside the parantheses (XXX) and return based on that

        1. Capture.PNG
          Capture.PNG
          20 kB
        2. Capture3.PNG
          Capture3.PNG
          47 kB
        3. Capture2.PNG
          Capture2.PNG
          21 kB

            Assignee:
            Unassigned
            Reporter:
            Andrew Morin
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: