Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-70865

Copying link in description or comment fields fails in new Jira issue view

XMLWordPrintable

      Summary

      If you copy a link that ends with a slash ( / ) or has an exclamation mark( ! ) and paste it in the description or comment field, it fails with the following error:

      We couldn't save your comment
      It might be empty, too long, or have invalid
      formatting. If you copy-pasted, try removing the
      formatting and adding it directly in the editor.

      Steps to Reproduce

      1. Type the following link as comment and save it:

        https://test.com/

        https://xyz123.atlassian.net/secure/admin/LookAndFeel!default.jspa

      2. Copy the link from the comment
      3. Past the link into another comment (or in the description field) and click Save

      Expected Results

      Comment/description saves

      Actual Results

      Following error appears in UI and browser's console:

      Workaround

      Click on the link and select Unlink before saving it, see screenshot below:

        1. Comment Error.png
          Comment Error.png
          654 kB
        2. Unlink comment.png
          Unlink comment.png
          73 kB
        3. D5UxmGRXsAAUBA8.jpg_large
          24 kB
        4. bug report.jpg
          bug report.jpg
          24 kB
        5. D7QcUj2XYAELhTK.png
          D7QcUj2XYAELhTK.png
          23 kB
        6. toomuchbug.txt
          30 kB

            [JRACLOUD-70865] Copying link in description or comment fields fails in new Jira issue view

            Ron Osikowicz added a comment -

            I get this several times a week, but only when I paste a screenshot into the Comment.  It does NOT happen with all screenshots.  If I close Jira and the browse, I can start a new Jira session without problems, for a while.

            Ron Osikowicz added a comment - I get this several times a week, but only when I paste a screenshot into the Comment.  It does NOT happen with all screenshots.  If I close Jira and the browse, I can start a new Jira session without problems, for a while.

            Deleted Account (Inactive) added a comment -

            Workaround with unlinking doesn't help me. I cannot edit or delete comment, basically I cannot do anything with my comment . 

            Deleted Account (Inactive) added a comment - Workaround with unlinking doesn't help me. I cannot edit or delete comment, basically I cannot do anything with my comment . 

            Ian Clelland added a comment - - edited

            Hi,

            This has affected me hundreds of times and I am upset that the new experience is so buggy.

            I just want to add that commenting works in this form from the JQL search (search: 'issue = MYPROJ-123' and comment from there) because the comment box there is the old-fashioned traditional comment box.

            I have noticed that a lot of basic features don't work properly in the new Jira experience that do and did work properly in the old experience.

            I really don't know why you are trying to replace things that work with things that don't.

            Thanks,
            Ian

            Ian Clelland added a comment - - edited Hi, This has affected me hundreds of times and I am upset that the new experience is so buggy. I just want to add that commenting works in this form from the JQL search (search: 'issue = MYPROJ-123' and comment from there) because the comment box there is the old-fashioned traditional comment box. I have noticed that a lot of basic features don't work properly in the new Jira experience that do and did work properly in the old experience. I really don't know why you are trying to replace things that work with things that don't. Thanks, Ian

            kenorb added a comment - - edited

            Got the same error when posting the following code despite placing it in the Code block:

            rg -v 404 logs/ | rg --no-filename -o "GET ([^ ?]+)" -r '$1'

            It seems it works here.

            kenorb added a comment - - edited Got the same error when posting the following code despite placing it in the Code block: rg -v 404 logs/ | rg --no-filename -o "GET ([^ ?]+)" -r '$1' It seems it works here.

              pkuo Peggy
              grahimi Yahya (Inactive)
              Affected customers:
              16 This affects my team
              Watchers:
              26 Start watching this issue

                Created:
                Updated:
                Resolved: