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

Replying to an email with an image attached creates a new attachment with the filename 'noname'

      Issue Summary

      When replying to an email notification which has an image attached using the Gmail client, a new image is attached to the issue with the filename `noname`

      Steps to Reproduce

      1. Create a new JSD project with email request
      2. Setup outgoing mail server
      3. Setup a customer account (cust) and a agent account (agent)
      4. Login to customer portal as cust
      5. Create a new request and assign agent as the Assignee
      6. Agent update the issue from Jira (comment with attachment), triggering notification to cust
        • cust replies to the notification with new attachment - watch for the JSD update and agent notification
        • cust replies to the last notification with no attachment - watch for the JSD update and agent notification

      Expected Results

      The image is sent with the original attachment name and would appear on JSD as a duplicate or ignored, not as `noname`

      Actual Results

      Image is attached with the filename `noname`

      Message metadata for attachments:

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            [JSDSERVER-6907] Replying to an email with an image attached creates a new attachment with the filename 'noname'

            It would be great to get this fixed considering the noname attachments in my instance are a result of the tiny images within the Jira Agent notifications. For instance, the tiny chat bubble to represent the comment section in a Jira notification, when replied to, creates an attachment called noname on the ticket.

            Atticus Bikos added a comment - It would be great to get this fixed considering the noname attachments in my instance are a result of the tiny images within the Jira Agent notifications. For instance, the tiny chat bubble to represent the comment section in a Jira notification, when replied to, creates an attachment called noname on the ticket.

            We are still waiting for this fix as screenshots out of order are very dangerous and easily misinterpreted.

            Sandra Toppin added a comment - We are still waiting for this fix as screenshots out of order are very dangerous and easily misinterpreted.

            Need resolution ASAP - we are a health IT company so displaying patient health information correctly is critical to business.

            rae edwards added a comment - Need resolution ASAP - we are a health IT company so displaying patient health information correctly is critical to business.

            Vasavi Nagalla added a comment - - edited

            would be good to get this resolved ASAP, especially being in healthcare, we tend to provide lots of screenshots.

            Vasavi Nagalla added a comment - - edited would be good to get this resolved ASAP, especially being in healthcare, we tend to provide lots of screenshots.

              Unassigned Unassigned
              01656e440512 Craig Shannon
              Affected customers:
              6 This affects my team
              Watchers:
              9 Start watching this issue

                Created:
                Updated: