Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-16388

Images added in full size to public comments show as a thumbnail in Customer Notifications

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: High High
    • None
    • 10.2.0, 10.3.9, 10.3.10
    • Customer Notification

      Issue

      If a full size image is included in a public comment in a JSM ticket, the 2 problems below will be observed in the Customer Notification:

      • the image will be shown as a blurry thumbnail instead of in full size
      • the image will not be clickable, giving no option for the recipient to see the full image

      Affected versions

      Any JSM (Jira Service Management) version from 10.2.0.

      Steps to replicate

      • Install JSM on any version from 10.2.0
      • Configure an outgoing mail server
      • Create a new JSM ticket
      • Add an image as an attachment to the ticket
      • Include the image in a public comment, using the syntax below, so that the image is in full size:
         !imageFileName.png! 
        
      • Wait for the Customer Notification to be sent

      Expected behavior

      The image should be in full size in the email, and it should also be possible click on it, as it used to be the case in JSM versions lower than 10.2.0 (for example in JSM 10.1.2 as illustrated below):

      Actual behavior

      The image has the thumbnail size and is therefore too blurry to be able to read any text:

      Workaround

      1. While logged in as an admin user, go to this URL on your browser:
        <BASE_URL>/secure/admin/SiteDarkFeatures!default.jspa
        
      2. In the section to add a new feature flag, add the following parameter:
        com.atlassian.jira.send.email.notifications.with.images.attached.disabled
        
      3. Click on Add

      Next time an image is included in full size in a public comment, the image will be in ful size in the customer notification, as it used to be the case in JSM versions lower than 10.2.0:

      Notes

      We suspect that this bug was caused as a side effect of the fix implemented in Jira/JSM 10.2.0 for JRASERVER-41675.

        1. JSM10.3.9.png
          159 kB
          Julien Rey
        2. JSM10.3.9_WithWorkaround.png
          419 kB
          Julien Rey
        3. JSM10.1.2.png
          409 kB
          Julien Rey

              Unassigned Unassigned
              jrey Julien Rey (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: