My issue is related to this to the following issue:
I turned on the renderer to wiki style renderer but I still can't see the attachments that were attached to the ticket from the customer end. Was wondering what else needs to be done?
Hi Jimmy,
I tried to replicate this issue here, but it works adding an attachment and also creating a ticket through email with a signature and attachments.
Is it happening only with attachments on the description?
Have you tried adding an attachment on the description after the ticket is created?
Regards,
Angélica
Hi Angélica,
I think I'm facing the same issue.
I am not able to see the attachments on the customer portal if the assignee simply inserts it on an issue. However if after inserting the attachement on the issue, I reference it by inserting it on a public comment, the attachment becomes visible to the customer inside the comment.
Do you know if there is any solution to show the attachment at the very moment it is inserted on the issue? I would like to do that because there are some cases on my project where it's required that the assignee inserts an attachment on a transition screen and it should be visible to the requester of the issue.
Thank you,
Bruno
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Welcome to Atlassian Community!
What you mentioned is an expected behavior, because in the customer portal the field "Attachments" is not visible, so if an agent only adds an attachment without sharing as a public comment, the customer won't be able to see, since that area that shows attachments in the agent view, is not visible to customers.
In this case, every time an attachment is added, the agent will have to share it as a comment for the customer to receive the notification and view the image in the portal.
Regards,
Angélica
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Need some clarification here on "...so if an agent only adds an attachment without sharing as a public comment, the customer won't be able to see..."
The agent wants to share attachments to the customer. The agent do "attach files" from the more menu, or by doing browse in the attachments section.
Case 1:
Case 2:
Conclusion: The agent must know that a comment must be written in order to share the files. The agent is not informed about that.
Desired Behaviour: The add attachments dialog shall inform the agent that a comment must be written in order to share the attachment.
OR
The function should write a default comment if no comment from the agent is provided.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Peter,
This problem is related in Bug https://jira.atlassian.com/browse/JSDSERVER-6706, upgrade to Jira Service Desk 4.8.0 ou higher to resolve.
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It's still broken, or broken again, in JSM 5.1.2 (datacenter).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Jimmy
Is the field on the screen?
Do you've attachments permissions in the project?
Is the field hidden?
Victor
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The field is not on the screen and the end user can't see the attachments that we put on the ticket.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Jimmy
Add the Attachment field to the screen.
Victor
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.