Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-15895

Using {code:sql} this is adding quote"> before the first single quote of each line.

      Summary

      Users trying to use {code:sql} and this is adding the following characters quote"> before the first single quote.

      Steps to Reproduce

      1 - Start to add a comment or a description in an Issue in JIRA;
      2 - Use the {code:sql}
      3 - This is breaking and is generating the characters quote">

      Example:
      Add a comment with the following:

      {code:sql}
      UPDATE table SET value = 'test';
      {code}

      This will produce the following output:
      UPDATE table SET value = quote">'test';

       

      **See attachments.

      Expected Results

      Adding a comment using code block sql and this not add "quote">", like this:
      {code:sql}
      UPDATE table SET value = 'test';
      {code}

      Workaround

      Modify the code block header to {code} instead of {code:sql}

        1. Expected.png
          Expected.png
          8 kB
        2. output bug.png
          output bug.png
          26 kB

            [JSWCLOUD-15895] Using {code:sql} this is adding quote"> before the first single quote of each line.

            A fix for this issue is ready and awaiting release. SQL query highlighting will be back to normal very soon.

            Thank you!

            Jeff Mattfield added a comment - A fix for this issue is ready and awaiting release. SQL query highlighting will be back to normal very soon. Thank you!

            Hi everyone,

            A fix for this issue is ready and awaiting release. SQL query highlighting will be back to normal very soon.

            Cheers,

            David Piper [JIRA Software]

            David Piper added a comment - Hi everyone, A fix for this issue is ready and awaiting release. SQL query highlighting will be back to normal very soon. Cheers, David Piper [JIRA Software]

            jhardin-aptos-com added a comment - - edited

            I vote for the priority to be higher than "medium", because this breaks all queries in comments on our tickets.

            +1

            jhardin-aptos-com added a comment - - edited I vote for the priority to be higher than "medium", because this breaks all queries in comments on our tickets. +1

            I vote for the priority to be higher than "medium", because this breaks all queries in comments on our tickets.

            Same here

            Mischa ter Smitten added a comment - I vote for the priority to be higher than "medium", because this breaks all queries in comments on our tickets. Same here

            mvbeek_oefenweb added a comment - - edited

            I vote for the priority to be higher than "medium", because this breaks all queries in comments on our tickets.

            (We use this functionality to share simple SQL queries when working on a ticket.)

            mvbeek_oefenweb added a comment - - edited I vote for the priority to be higher than "medium", because this breaks all queries in comments on our tickets. (We use this functionality to share simple SQL queries when working on a ticket.)

              dpiper David Piper
              lsanguitam Leonardo Sanguitam (Inactive)
              Affected customers:
              10 This affects my team
              Watchers:
              22 Start watching this issue

                Created:
                Updated:
                Resolved: