...
The configured format of the uploaded attachment.
Pattern | Description |
|---|---|
%O | operation as |
%Y | sent date as |
%T | (sent date as |
%P | personal name of the remote sender address |
%E | file extensions as |
Default Format:
| Code Block |
|---|
%O-%Y-%T-%P.%E |
Issue create attachments for JSM requests
Due to the JSM REST API behaviour, attachments are not supplied on the issue create request unless the attachments field is on the request creation form.
What happens if the attachment field is not required?
If the attachment field is not on the request create form, attachments cannot be supplied on request creation. Any attachments yet to be added to the issue will attempt to be added as an issue update after request creation is successful.
How does this affect outbound notifications?
If you are using the default Jira mail handler, this can cause multiple notifications to be sent (The issue creation, plus subsequent issue updates for attachments being added post-create). Adding the attachment field will allow JEMHC to supply attachments in a single create request, no longer sending notifications on issue updates.
Please note: Any attachments unable to be uploaded on issue create will be added on update and may still trigger a secondary Jira Mail Handler notification.
If you are using JEMHC outbound notifications, the events will be bundled into a single notification.
If you do not wish to see the attachment uploaded as an issue update, adding the attachment field will allow JEMHC to attempt uploading attachments on service request creation.