TODOAttachment configuration allows attachments from incoming emails to be added to created issues.
| Info |
|---|
Note: When attachments, images, or attachment email copies are included, the downloaded data will could towards the total plan usage. |
| Table of Contents | ||||
|---|---|---|---|---|
|
Upload Attachments
This setting configures if attachments found in the incoming email should be added to created issues. Available options are:
All - Attachments will be added to created issues.
Attachment Duplication Strategy - Only selectable when ‘Upload Attachments’ set to ‘All’.
None - attachments will not be added to created issues.
Attachment Duplication Strategy - Requires 'Upload Attachments' set to ‘All’
When attachments should be added to created issues, the strategy option is shown.
Available options are:
None - Attachment duplication will be avoided. Used to reduce attachment and image duplication from replied emails processed by JEMH Cloud.
Retrieve issue attachments and hash - Gets existing attachment data on the existing issue. Only adds the new attachment if the hashes differ. The hash strategy adds to Plan data usage when an existing attachment is the same size as the new file but its hash value isn't yet known.
Add Email To Issue
‘Add Email to Issue’ configuration allows incoming emails to include a copy of the inbound email on the issue.
| Info |
|---|
Note: Attaching email to issue will consume (at least) double data when processing emails, due to uploading the entire email content size as an attachment. |
Attach Email
When enabled, attaches the incoming email as a .eml file. Available options are:
Off
On Create
On Comment
On Create/Comment
Attach HTML Body
When enabled, attaches the incoming email body (if present) as a .html file. Available options are:
Off
On Create
On Comment
On Create/Comment
Attach Text Body
When enabled, attaches the incoming email body (if present) as a .txt file. Available options are:
Off
On Create
On Comment
On Create/Comment
Disable Zipping Original Content
When enabled, original email content will be attached to the issue without compressing into a .zip file.
When disabled (default value), original email content will be compressed to reduce plan consumption.
Attached Email File Name Format:
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.