You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow attachments for tickets. Attachments would be uploaded and recorded in a new table. They would be accessible under the ticket reply associated with them (or under the main ticket if uploaded during ticket creation).
Table: ticket_attachments
ticket_attachment_id
ticket_attachment_name (friendly name)
ticket_attachment_ticket_id
ticket_attachment_ticket_reply_id (0 is attached to the main ticket?)
ticket_attachment_ref (md5 / random name)
ticket_attachment_created_at
The text was updated successfully, but these errors were encountered:
Reviewing the GUI and this commit, I only see the possibility to add attachments in the customer portal and by email. But I cannot add attachments as an admin in the "default" system view, or am I missing something (most likely I am... 🤷♂️)
Reviewing the GUI and this commit, I only see the possibility to add attachments in the customer portal and by email. But I cannot add attachments as an admin in the "default" system view, or am I missing something (most likely I am... 🤷♂️)
You are completely correct. We need to add it on the agent side too! This should be relatively easy.
Agents should be able to attach files as part of adding a ticket reply/comment.
For client-visible replies that send an email, either the file should either be attached to the email or a link to the file included at the bottom.
Allow attachments for tickets. Attachments would be uploaded and recorded in a new table. They would be accessible under the ticket reply associated with them (or under the main ticket if uploaded during ticket creation).
Table: ticket_attachments
ticket_attachment_id
ticket_attachment_name (friendly name)
ticket_attachment_ticket_id
ticket_attachment_ticket_reply_id (0 is attached to the main ticket?)
ticket_attachment_ref (md5 / random name)
ticket_attachment_created_at
The text was updated successfully, but these errors were encountered: