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

JQL parser should handle reserved characters better and more consistently.

    XMLWordPrintable

Details

    • Severity 2 - Major
    • Hide
      Atlassian Update – 04 December 2017

      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 – 04 December 2017 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

    Description

      NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.

      The jql autocomplete parser has some weird behaviour around reserved characters see JRA-22927. Full-stops are not an uncommon things in version numbers.

      Right now if one has versions 4.0, 4.0.1, 4.1 and 4.2. And types 'affectedVersion = 4.0' 4.1 and 4.2 will still be in the list but there will be an ! at the top of the jql parser box.

      If you type 'affectedVersion = "4.0' (note the double-quote (") is not yet closed), the autocomplete list will be winnowed down to just 4.0 and 4.0.1 but there will be an ! at the top of the jql parser box.

      If you type 'affectedVersion = ""' and then within the "" type 4.0 the list will be winnowed down to 4.0 and 4.0.1 and the jql parser will keep its tick.

      I would expect that all three would behave the same way. With perhaps the first 2 keeping the ! as the value is not quoted correctly.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              rsmart metapoint
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: