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

Adding an attachment with an identical file name will change all existing references in a request

XMLWordPrintable

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

      Summary

      If an attachment gets added to a customer request, which has an identical name to another attachment under the same request, all existing references to the original attachment will get adjusted to reflect the new attachment.

      Steps to Reproduce

      1. As a customer, add an attachment to a request. From the customer view, this issue will have a linked url displayed as <baseurl>/servicedesk/customershim/secure/attachment/<attachmentID1>/<attachmentID1>_<attachmentname>
      2. As an Agent, add an attachment to the same request, and choose "Add to issue only". The file name should be identical to the file as attached under step 1. This attachment is not visible from the customer view

      Expected Results

      The attachment added by the customer should remain being displayed as <baseurl>/servicedesk/customershim/secure/attachment/<attachmentID1>/<attachmentID1>_<attachmentname> and be accessible as such.

      Actual Results

      The url referencing the attachment in the customer view has changed to <baseurl>/servicedesk/customershim/secure/attachment/<attachmentID2>/<attachmentID2>_<attachmentname>

      Notes

      For the above setup, the files do not have to be identical, just the file name needs to be identical. This has been tested with both identical files, as well as with different files renamed to have identical names.

          Form Name

            [JSDSERVER-3615] Adding an attachment with an identical file name will change all existing references in a request

            Jonathan added a comment -

            see JSDSERVER-5054

            Jonathan added a comment - see JSDSERVER-5054

            Patrick van der Rijst added a comment -

            This results in users that click on an attachment reference via an e-mail to a previous version of the attachment, to end up on a 401 - not permitted page which is not acceptable.

            Patrick van der Rijst added a comment - This results in users that click on an attachment reference via an e-mail to a previous version of the attachment, to end up on a 401 - not permitted page which is not acceptable.

            Amis Cabrera Gonzalez added a comment -

            I know this issue doesn't prevent users to work or to report issues but soon it is going to be 2 years since this ticket was created (so probably even longer since the bug was reported).

            Amis Cabrera Gonzalez added a comment - I know this issue doesn't prevent users to work or to report issues but soon it is going to be 2 years since this ticket was created (so probably even longer since the bug was reported).

              Unassigned Unassigned
              mnassette MJ (Inactive)
              Affected customers:
              11 This affects my team
              Watchers:
              14 Start watching this issue

                Created:
                Updated:
                Resolved: