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

Adding attachment by copying the link from Agent view is not visible to the Customer

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

      Summary:
      Based on this documentation, it shows that it's possible to add attachment by copying the link from Agent view:

      To ensure that the customer sees the attachment, right click on the attachment to copy link address and paste the link into a comment surrounded by square brackets as follows: [description of attachment|attachment link]. Click preview to confirm the attachment link has copied correctly:

      When users copy the link, the URL will be https://<instance-name>/secure/attachment/10200/test.pdf instead of https://<instance-name>/servicedesk/customershim/secure/attachment/10200/10200_test.pdf. Since Customer does not have access to JIRA, the attachment can't be accessed.

      Steps to reproduce:

      1. Customer create a new issue
      2. Agent adds an attachment and right click to copy the attachment link
      3. The URL will be https://<instance-name>/secure/attachment/10200/test.pdf
      4. Agent adds the attachment using this format[description of attachment|attachment link]

      Expected Result:

      • Customer should be able to access it without having JIRA application access

      Current Result:

      • Customer is not able to access it

      Workaround:

      • Use this format [ ^description.ext ] to add the attachment
      • The workaround above no longer works as even when linking the files in the chat; the file is pointing to https://<instance-name>/secure/attachment/10200/test.pdf (JIRA) and no longer point to Service Desk. For now if the customer wants to directly access the attachments; the agent have to manually provide the Service Desk URL instead; which is https://<instance-name>/servicedesk/customershim/secure/attachment/<ATTACHMENT_ID>/<ATTACHMENT_ID>_<FILE_NAME>

          Form Name

            [JSDSERVER-1726] Adding attachment by copying the link from Agent view is not visible to the Customer

            Owen made changes -
            Workflow Original: JSD Bug Workflow v5 - TEMP [ 2305218 ] New: JAC Bug Workflow v3 [ 3125722 ]
            Status Original: Done [ 10044 ] New: Closed [ 6 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 [ 2059159 ] New: JSD Bug Workflow v5 - TEMP [ 2305218 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 - TEMP [ 2056562 ] New: JSD Bug Workflow v5 [ 2059159 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 [ 1956187 ] New: JSD Bug Workflow v5 - TEMP [ 2056562 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v4 [ 1615567 ] New: JSD Bug Workflow v5 [ 1956187 ]
            jonah (Inactive) made changes -
            Description Original: *Summary:*
            Based on this [documentation|https://confluence.atlassian.com/display/Cloud/Getting+started+for+service+desk+agents#Gettingstartedforservicedeskagents-Workoncustomerissues], it shows that it's possible to add attachment by copying the link from Agent view:
            {quote}
            To ensure that the customer sees the attachment, right click on the attachment to copy link address and paste the link into a comment surrounded by square brackets as follows: [description of attachment|attachment link]. Click preview to confirm the attachment link has copied correctly:
            {quote}

            When users copy the link, the URL will be {{https://&lt;instance-name&gt;/secure/attachment/10200/test.pdf}} instead of {{https://&lt;instance-name&gt;/servicedesk/customershim/secure/attachment/10200/10200_test.pdf}}. Since Customer does not have access to JIRA, the attachment can't be accessed.

            *Steps to reproduce:*
            # Customer create a new issue
            # Agent adds an attachment and right click to copy the attachment link
            # The URL will be {{https://&lt;instance-name&gt;/secure/attachment/10200/test.pdf}}
            # Agent adds the attachment using this format[description of attachment|attachment link]

            *Expected Result:*
            - Customer should be able to access it without having JIRA application access

            *Current Result:*
            - Customer is not able to access it

            *Workaround:*
            - -Use this format [ ^description.ext ] to add the attachment-

            - The workaround above no longer works as even when linking the files in the chat; the file is pointing to {{https://&lt;instance-name&gt;/secure/attachment/10200/test.pdf}} (JIRA) and no longer point to Service Desk. For now if the customer wants to directly access the attachments; the agent have to manually provide the Service Desk URL instead; which is {{https://&lt;instance-name&gt;/servicedesk/customershim/secure/attachment/&lt;ATTACHMENT_ID&gt;/&lt;ATTACHMENT_ID&gt;_&lt;FILE_NAME>}}
            New: {panel:bgColor=#e7f4fa}
              *NOTE:* This bug report is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSDCLOUD-1726].
              {panel}

            *Summary:*
            Based on this [documentation|https://confluence.atlassian.com/display/Cloud/Getting+started+for+service+desk+agents#Gettingstartedforservicedeskagents-Workoncustomerissues], it shows that it's possible to add attachment by copying the link from Agent view:
            {quote}
            To ensure that the customer sees the attachment, right click on the attachment to copy link address and paste the link into a comment surrounded by square brackets as follows: [description of attachment|attachment link]. Click preview to confirm the attachment link has copied correctly:
            {quote}

            When users copy the link, the URL will be {{https://&lt;instance-name&gt;/secure/attachment/10200/test.pdf}} instead of {{https://&lt;instance-name&gt;/servicedesk/customershim/secure/attachment/10200/10200_test.pdf}}. Since Customer does not have access to JIRA, the attachment can't be accessed.

            *Steps to reproduce:*
            # Customer create a new issue
            # Agent adds an attachment and right click to copy the attachment link
            # The URL will be {{https://&lt;instance-name&gt;/secure/attachment/10200/test.pdf}}
            # Agent adds the attachment using this format[description of attachment|attachment link]

            *Expected Result:*
            - Customer should be able to access it without having JIRA application access

            *Current Result:*
            - Customer is not able to access it

            *Workaround:*
            - -Use this format [ ^description.ext ] to add the attachment-

            - The workaround above no longer works as even when linking the files in the chat; the file is pointing to {{https://&lt;instance-name&gt;/secure/attachment/10200/test.pdf}} (JIRA) and no longer point to Service Desk. For now if the customer wants to directly access the attachments; the agent have to manually provide the Service Desk URL instead; which is {{https://&lt;instance-name&gt;/servicedesk/customershim/secure/attachment/&lt;ATTACHMENT_ID&gt;/&lt;ATTACHMENT_ID&gt;_&lt;FILE_NAME>}}
            jonah (Inactive) made changes -
            Link New: This issue relates to JSDCLOUD-1726 [ JSDCLOUD-1726 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v2 [ 1603061 ] New: JSD Bug Workflow v4 [ 1615567 ]
            Owen made changes -
            Workflow Original: JSD Bug Workflow [ 1399242 ] New: JSD Bug Workflow v2 [ 1603061 ]
            Owen Sanico [Administrative Account] made changes -
            Workflow Original: TTT: Simple Issue Tracking Workflow [ 847533 ] New: JSD Bug Workflow [ 1399242 ]

              skarp Sarah Karp
              rsaputra Adven
              Affected customers:
              0 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: