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

Image Filenames with Existing Issue Key will not be Rendered in Image Macro

    XMLWordPrintable

Details

    Description

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

      If an image's filename contains an existing issue key, the image will not be rendered when using the image macro.

      Steps to reproduce:

      1. Create 5 issues. Issue keys will be generated (for example: GH-1, GH-2, GH-3, GH-4, GH-5)
      2. Open up issue with issue key GH-2.
      3. Attach an image with its filename containing any of the above issue key (for example: GH-3 For Testing.jpg)
      4. Open up the comment box, and input any of the following to execute the image macro: 
        !GH-3 For Testing.jpg!

        !GH-3 For Testing.jpg|thumb!
      5. Preview the comment. The following output is shown, and the image is not rendered:

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-32688 An attachment with an issue key in its file name cannot be rendered as an inline image in an issue

          • Low - Low priority issues
          • Closed
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JRACLOUD-66479 Using Issue #'s within attachment filenames will cause Jira t be unable to render them when embedding them within a comment, or description.

          • Low - Low priority issues
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JRACLOUD-26230 Image Filenames with Existing Issue Key will not be Rendered in Image Macro

          • Low - Low priority issues
          • Closed

          Activity

            People

              Unassigned Unassigned
              jalex Justin Alex [Atlassian] (Inactive)
              Votes:
              5 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: