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

creating issue with utf8 new line character (U+2028) in summary breaks issue search page

XMLWordPrintable

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

      Creating issue with
      "Unicode Character 'LINE SEPARATOR' (U+2028)" in summary breaks issue searcher.
      Steps to reproduce:
      1. go to some page eg. issues->search for issues
      2. click create button to create new issue
      3. paste text with u+2028 character eg. "Make Payments for sessions 
"
      the quoted text should have this character at the end, You can check this by going to ge. http://www.url-encode-decode.com/ and encode the string, the output string should have %E2%80%A8 near the end.
      4. create issue
      5. go back to eg. dashboard
      6. return to issues->search for issues
      7. the page is broken due to failing JS

      after investigation it turned out that the culprit is the old jquery library that we use (i belive 1.7.2) and there is some json string matching there that the string with unicode new line character fails

      var Yb=/^(?:\{.*\}|\[.*\])$/

      and later 

      c="true"===c?!0:"false"===c?!1:"null"===c?null:d.isNumeric(c)?+c:Yb.test(c)?d.parseJSON(c):c

      that fails and returns string instead of parsed json object.

      the workaround is to edit specific issue and delete these "invalid" character.

        1. 20150701-bug1.png
          20150701-bug1.png
          201 kB

            [JRASERVER-44091] creating issue with utf8 new line character (U+2028) in summary breaks issue search page

            Ewelina Fiedorowicz added a comment -
            Atlassian Update – 22.07.2021

            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,
            Ewelina Fiedorowicz

            Ewelina Fiedorowicz added a comment - Atlassian Update – 22.07.2021 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, Ewelina Fiedorowicz

              Unassigned Unassigned
              tkanafa Tomasz Kanafa
              Affected customers:
              1 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: