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

Attachments added by email with the same filename aren't linking to the correct attachment

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Low Low
    • None
    • 4.7.1
    • Email - Incoming
    • None

      Issue Summary

      When attachments are added via email through JSD mail handler with the same filename then there is a suffix added to the new attachment as per this bug JSDSERVER-5054

      But, the new attachment is being pushed to the bottom of the comment, and then references to that file always point to the oldest version of that file.

      Steps to Reproduce

      1. Configure email in Project settings > Email requests
      2. Send an email with say three images (image001.png, image002.png, image003.png)
      3. Check the comment in Jira service desk ticket, there should be three images aligned without any issues
      4. Reply on the above email and expand the trial
      5. In the new email body, add another three images, but name one of the image with same name as in step2, we will consider a new image with the same name (image001.png)
      6. Send the email
      7. To fix the bug JSDSERVER-5054, there is a suffix added to the new attachment (image001-1.png) in a scenario when there are two attachments with the same names
      8. Above statement is an expected behavior
      9. But, if we see the new comment in Jira service desk ticket agent view and customer portal view, the new attachment is pushed to the bottom and the old image is being referenced in place of new attachment

      Expected Results

      The newly added attachment should not be pushed to the bottom of the comment and old image should not be referenced in place of new attachment 

      Actual Results

      Agent View:

      Customer Portal view:

      Workaround

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

        1. Agent View.png
          Agent View.png
          341 kB
        2. customer portal view.png
          customer portal view.png
          371 kB

          Form Name

            [JSDSERVER-6831] Attachments added by email with the same filename aren't linking to the correct attachment

            Divyanshi made changes -
            Link New: This issue duplicates JSDSERVER-6809 [ JSDSERVER-6809 ]
            Divyanshi made changes -
            Resolution New: Duplicate [ 3 ]
            Status Original: Needs Triage [ 10030 ] New: Closed [ 6 ]
            Bugfix Automation Bot made changes -
            Support reference count New: 1
            Sriteja Kattamuru (Inactive) made changes -
            Description Original: h3. Issue Summary

            When attachments are added via email through JSD mail handler with the same filename then there is a suffix added to the new attachment as per this bug JSDSERVER-5054

            But, the new attachment is being pushed to the bottom of the comment, and then references to that file always point to the oldest version of that file.
            h3. Steps to Reproduce
             # Configure email in Project settings > Email requests
             # Send an email with say three images (image001.png, image002.png, image003.png)
             # Check the comment in Jira service desk ticket, there should be three images aligned without any issues
             # Reply on the above email and expand the trial
             # In the new email body, add another three images, but name one of the image with same name as in step2, we will consider a new image with the same name (image001.png)
             # Send the email
             # To fix the bug -JSDSERVER-5054-, there is a suffix added to the new attachment (image001-1.png) in a scenario when there are two attachments with the same names
             # Above statement is an expected behavior
             # But, if we see the new comment in Jira service desk ticket agent view and customer portal view, the new attachment is pushed to the bottom and the old image is being referenced in place of new attachment

              
            h3. Expected Results

            The newly added attachment should not be pushed to the bottom of the comment and old image should not be referenced in place of new attachment 
            h3. Actual Results

            *Agent View:*

            !Agent View.png|thumbnail!

            *Customer Portal view:*
             !customer portal view.png|thumbnail!
            h3. Workaround

            Currently, there is no known workaround for this behavior. A workaround will be added here when available.             		New: h3. Issue Summary

            When attachments are added via email through JSD mail handler with the same filename then there is a suffix added to the new attachment as per this bug JSDSERVER-5054

            But, the new attachment is being pushed to the bottom of the comment, and then references to that file always point to the oldest version of that file.
            h3. Steps to Reproduce
             # Configure email in Project settings > Email requests
             # Send an email with say three images (image001.png, image002.png, image003.png)
             # Check the comment in Jira service desk ticket, there should be three images aligned without any issues
             # Reply on the above email and expand the trial
             # In the new email body, add another three images, but name one of the image with same name as in step2, we will consider a new image with the same name (image001.png)
             # Send the email
             # To fix the bug -JSDSERVER-5054-, there is a suffix added to the new attachment (image001-1.png) in a scenario when there are two attachments with the same names
             # Above statement is an expected behavior
             # But, if we see the new comment in Jira service desk ticket agent view and customer portal view, the new attachment is pushed to the bottom and the old image is being referenced in place of new attachment

            h3. Expected Results

            The newly added attachment should not be pushed to the bottom of the comment and old image should not be referenced in place of new attachment 
            h3. Actual Results

            *Agent View:*

            !Agent View.png|thumbnail!

            *Customer Portal view:*
             !customer portal view.png|thumbnail!
            h3. Workaround

            Currently, there is no known workaround for this behavior. A workaround will be added here when available.
            Sriteja Kattamuru (Inactive) made changes -
            Description Original: h3. Issue Summary

            When attachments are added via email through JSD mail handler with the same filename then there is a suffix added to the new attachment as per this bug JSDSERVER-5054

            But, the new attachment is being pushed to the bottom of the comment, and then references to that file always point to the oldest version of that file.
            h3. Steps to Reproduce
             # Configure email in Project settings > Email requests
             # Send an email with say three images (image001.png, image002.png, image003.png)
             # Check the comment in Jira service desk ticket, there should be three images aligned without any issues
             # Reply on the above email and expand the trial
             # In the new email body, add another three images, but name one of the image with same name as in step2, we will consider a new image with the same name (image001.png)
             # Send the email
             # To fix the bug -JSDSERVER-5054-, there is a suffix added to the new attachment (image001-1.png) in a scenario when there are two attachments with the same names
             # Above statement is an expected behavior
             # But, if we see the new comment in Jira service desk ticket agent view and customer portal view, the new attachment is pushed to the bottom and the old image is being referenced

              
            h3. Expected Results

            The newly added attachment should not be pushed to the bottom of the comment and old image should not be referenced to old attachment
            h3. Actual Results

            *Agent View:*

            !Agent View.png|thumbnail!

            *Customer Portal view:*
             !customer portal view.png|thumbnail!
            h3. Workaround
            Currently, there is no known workaround for this behavior. A workaround will be added here when available.             		New: h3. Issue Summary

            When attachments are added via email through JSD mail handler with the same filename then there is a suffix added to the new attachment as per this bug JSDSERVER-5054

            But, the new attachment is being pushed to the bottom of the comment, and then references to that file always point to the oldest version of that file.
            h3. Steps to Reproduce
             # Configure email in Project settings > Email requests
             # Send an email with say three images (image001.png, image002.png, image003.png)
             # Check the comment in Jira service desk ticket, there should be three images aligned without any issues
             # Reply on the above email and expand the trial
             # In the new email body, add another three images, but name one of the image with same name as in step2, we will consider a new image with the same name (image001.png)
             # Send the email
             # To fix the bug -JSDSERVER-5054-, there is a suffix added to the new attachment (image001-1.png) in a scenario when there are two attachments with the same names
             # Above statement is an expected behavior
             # But, if we see the new comment in Jira service desk ticket agent view and customer portal view, the new attachment is pushed to the bottom and the old image is being referenced in place of new attachment

              
            h3. Expected Results

            The newly added attachment should not be pushed to the bottom of the comment and old image should not be referenced in place of new attachment 
            h3. Actual Results

            *Agent View:*

            !Agent View.png|thumbnail!

            *Customer Portal view:*
             !customer portal view.png|thumbnail!
            h3. Workaround

            Currently, there is no known workaround for this behavior. A workaround will be added here when available.
            Sriteja Kattamuru (Inactive) made changes -
            Description Original: h3. Issue Summary

            When attachments are added via email through JSD mail handler with the same filename then there is a suffix added to the new attachment as per this bug JSDSERVER-5054

            But, the new attachment is being pushed to the bottom of the comment, and then references to that file always point to the oldest version of that file.
            h3. Steps to Reproduce
             # Configure email in Project settings > Email requests
             # Send an email with say three images (image001.png, image002.png, image003.png)
             # Check the comment in Jira service desk ticket, there should be three images aligned without any issues
             # Reply on the above email and expand the trial
             # In the new email body, add another three images, but name one of the image with same name as in step2, we will consider a new image with the same name (image001.png)
             # Send the email
             # To fix the bug -JSDSERVER-5054-, there is a suffix added to the new attachment (image001-1.png) in a scenario when there are two attachments with the same names
             # Above statement is an expected behavior
             # But, if we see the new comment in Jira service desk ticket agent view and customer portal view, the new attachment is pushed to the bottom and the old image is being referenced

              
            h3. Expected Results

            The newly added attachment should not be pushed to the bottom of the comment and old image should not be referenced 
            h3. Actual Results

            *Agent View:*

            !Agent View.png|thumbnail!

            *Customer Portal view:*
             !customer portal view.png|thumbnail!
            h3. Workaround

            sfgfdsG             		New: h3. Issue Summary

            When attachments are added via email through JSD mail handler with the same filename then there is a suffix added to the new attachment as per this bug JSDSERVER-5054

            But, the new attachment is being pushed to the bottom of the comment, and then references to that file always point to the oldest version of that file.
            h3. Steps to Reproduce
             # Configure email in Project settings > Email requests
             # Send an email with say three images (image001.png, image002.png, image003.png)
             # Check the comment in Jira service desk ticket, there should be three images aligned without any issues
             # Reply on the above email and expand the trial
             # In the new email body, add another three images, but name one of the image with same name as in step2, we will consider a new image with the same name (image001.png)
             # Send the email
             # To fix the bug -JSDSERVER-5054-, there is a suffix added to the new attachment (image001-1.png) in a scenario when there are two attachments with the same names
             # Above statement is an expected behavior
             # But, if we see the new comment in Jira service desk ticket agent view and customer portal view, the new attachment is pushed to the bottom and the old image is being referenced

              
            h3. Expected Results

            The newly added attachment should not be pushed to the bottom of the comment and old image should not be referenced to old attachment
            h3. Actual Results

            *Agent View:*

            !Agent View.png|thumbnail!

            *Customer Portal view:*
             !customer portal view.png|thumbnail!
            h3. Workaround
            Currently, there is no known workaround for this behavior. A workaround will be added here when available.
            Sriteja Kattamuru (Inactive) made changes -
            Description Original: h3. Issue Summary

            When attachments are added via email through JSD mail handler with the same filename then there is a suffix added to the new attachment as per this bug JSDSERVER-5054

            But, the new attachment is being pushed to the bottom of the comment, and then references to that file always point to the oldest version of that file.
            h3. Steps to Reproduce
             # Step 1
             # Step 2
             # sdg
             # sg

            h3. Expected Results

            dfbhf
            h3. Actual Results

            ghm 
            h3. Workaround

            sfgfdsG             		New: h3. Issue Summary

            When attachments are added via email through JSD mail handler with the same filename then there is a suffix added to the new attachment as per this bug JSDSERVER-5054

            But, the new attachment is being pushed to the bottom of the comment, and then references to that file always point to the oldest version of that file.
            h3. Steps to Reproduce
             # Configure email in Project settings > Email requests
             # Send an email with say three images (image001.png, image002.png, image003.png)
             # Check the comment in Jira service desk ticket, there should be three images aligned without any issues
             # Reply on the above email and expand the trial
             # In the new email body, add another three images, but name one of the image with same name as in step2, we will consider a new image with the same name (image001.png)
             # Send the email
             # To fix the bug -JSDSERVER-5054-, there is a suffix added to the new attachment (image001-1.png) in a scenario when there are two attachments with the same names
             # Above statement is an expected behavior
             # But, if we see the new comment in Jira service desk ticket agent view and customer portal view, the new attachment is pushed to the bottom and the old image is being referenced

              
            h3. Expected Results

            The newly added attachment should not be pushed to the bottom of the comment and old image should not be referenced 
            h3. Actual Results

            *Agent View:*

            !Agent View.png|thumbnail!

            *Customer Portal view:*
             !customer portal view.png|thumbnail!
            h3. Workaround

            sfgfdsG
            Sriteja Kattamuru (Inactive) made changes -
            Attachment New: customer portal view.png [ 387423 ]
            Sriteja Kattamuru (Inactive) made changes -
            Attachment New: Agent View.png [ 387422 ]
            Sriteja Kattamuru (Inactive) created issue -

              Unassigned Unassigned
              skattamuru@atlassian.com Sriteja Kattamuru (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: