• Type: Bug
• Resolution: Duplicate
• Priority: Medium
• Fix Version/s: None
• Affects Version/s: None
• Component/s: Customer Portal
• Labels:

  None

[JSDSERVER-1769] Attachment links are directing to JIRA instead of Service Desk

Owen made changes - 27/Mar/2019 5:46 AM

Workflow	Original: JSD Bug Workflow v5 - TEMP [ 2304220 ]	New: JAC Bug Workflow v3 [ 3125245 ]
Status	Original: Done [ 10044 ]	New: Closed [ 6 ]

Katherine Yabut made changes - 06/Jun/2017 3:16 AM

Workflow

Original: JSD Bug Workflow v5 [ 2058197 ]

New: JSD Bug Workflow v5 - TEMP [ 2304220 ]

Katherine Yabut made changes - 31/May/2017 12:38 AM

Workflow

Original: JSD Bug Workflow v5 - TEMP [ 2055749 ]

New: JSD Bug Workflow v5 [ 2058197 ]

Katherine Yabut made changes - 31/May/2017 12:35 AM

Workflow

Original: JSD Bug Workflow v5 [ 1956192 ]

New: JSD Bug Workflow v5 - TEMP [ 2055749 ]

Katherine Yabut made changes - 03/Apr/2017 5:18 AM

Workflow

Original: JSD Bug Workflow v4 [ 1616116 ]

New: JSD Bug Workflow v5 [ 1956192 ]

jonah (Inactive) made changes - 02/Apr/2017 11:46 AM

Description

Original: *Summary:* Adding an attachment link to a comment used to link the Service Desk attachment link {{https://<instance-name>/servicedesk/customershim/secure/attachment/10200/10200_test.pdf}} instead of {{https://<instance-name>/secure/attachment/10200/test.pdf}}. Since Customer does not have access to JIRA, the attachment can't be accessed. This is related to https://jira.atlassian.com/browse/JSD-1726 where the workaround provided is to use [^test.png] instead of [description of attachment|attachment link] . *Steps to reproduce:* # Agent adds the attachment using this format [^test.png] *Expected Result:* - Customer should be able to access it without having JIRA application access *Current Result:* - Customer is not able to access it. *Workaround:* - 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>}}

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-1769].   {panel} *Summary:* Adding an attachment link to a comment used to link the Service Desk attachment link {{https://<instance-name>/servicedesk/customershim/secure/attachment/10200/10200_test.pdf}} instead of {{https://<instance-name>/secure/attachment/10200/test.pdf}}. Since Customer does not have access to JIRA, the attachment can't be accessed. This is related to https://jira.atlassian.com/browse/JSD-1726 where the workaround provided is to use [^test.png] instead of [description of attachment|attachment link] . *Steps to reproduce:* # Agent adds the attachment using this format [^test.png] *Expected Result:* - Customer should be able to access it without having JIRA application access *Current Result:* - Customer is not able to access it. *Workaround:* - 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>}}

jonah (Inactive) made changes - 02/Apr/2017 11:46 AM

Link

New: This issue relates to JSDCLOUD-1769 [ JSDCLOUD-1769 ]

Katherine Yabut made changes - 19/Oct/2016 6:49 AM

Workflow

Original: JSD Bug Workflow v2 [ 1603319 ]

New: JSD Bug Workflow v4 [ 1616116 ]

Marty (Inactive) made changes - 07/Oct/2016 7:07 AM

Component/s		New: Customer Portal [ 26191 ]
Component/s	Original: Attachments [ 44401 ]

Owen made changes - 22/Sep/2016 3:24 AM

Workflow

Original: JSD Bug Workflow [ 1399243 ]

New: JSD Bug Workflow v2 [ 1603319 ]

Load more older events