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

Attachment with Alias is not downloadable from Portal

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Low Low
    • None
    • 3.15.1, 3.15.3
    • Customer Portal
    • None

      Summary

      Apparently, if we put an alias into an attachment, it will throw a "403 - Forbidden Error" when clicked.

      Steps to Reproduce

      1. Create a Service Desk request
      2. View it from Agent View.
      3. Compose a new comment and attach a zip file using the 'Clip' option.
      4. After it is added to the comment, add an alias like: 
        [Alias|file.zip]
      5. Click "Share with customer" to add a public comment.
      6. Click "View customer request" on the right panel to view it in the portal.
      7. Click the Attached file.

      Expected Results

      The file will be downloaded

      Actual Results

      A "403 - Forbidden Error" will come out instead

      Notes

      Somehow, if the same file is attached again without an alias, both links will work.

        1. screenshot-1.png
          screenshot-1.png
          17 kB

          Form Name

            [JSDSERVER-6151] Attachment with Alias is not downloadable from Portal

            Bartosz Ornatowski added a comment -

            This issue duplicates https://jira.atlassian.com/browse/JSDSERVER-6082

            Please vote and watch that ticket instead.

            Thank you,

            Jira Service Desk Team

            Bartosz Ornatowski added a comment - This issue duplicates  https://jira.atlassian.com/browse/JSDSERVER-6082 Please vote and watch that ticket instead. Thank you, Jira Service Desk Team

            axxonadmin added a comment -

            same here.

            But it doesn't matter whether there's an alias or not, portal always returns 403.

            No errors, no messages produced in logs. Nothing. It just does not work.

            axxonadmin added a comment - same here. But it doesn't matter whether there's an alias or not, portal always returns 403. No errors, no messages produced in logs. Nothing. It just does not work.

              Unassigned Unassigned
              jrahmadiputra Julian (Inactive)
              Affected customers:
              4 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: