The below table is to compare the mailing capabilities of Jira and Email this Issue (both Server and Cloud versions).
| Note | ||
|---|---|---|
| ||
Not all features are listed here to a full extent due to minor differences in the different products and deployment versions, however, we have tried to highlight the biggest benefits one solution has over another. |
Feature | Jira out-of-the-box | Jira Service Desk (Server version) | Email This Issue CLOUD | Email This Issue SERVER |
|---|---|---|---|---|
Outgoing Email Options | ||||
| Custom email templates | Supported (customer notifications only) | Supported | Supported | |
Notifications | ||||
| Support for single email addresses stored in custom fields via event notifications | Supported | Supported | ||
| Event notifications in Notification schemes | Supported | Supported | Supported | |
| Event notifications with JQL conditions | Supported (using automation) | Supported | Supported | |
Manual Email Defaults | ||||
| Manual email options editing |
| Supported | ||||
| Send issue details to users and to external email addresses (Email button) | Supported | Supported | ||
| Miscellaneous | ||||
| Send emails from a workflow transitions | Supported | Supported | ||
| Deleting SMTP prefix |
| from outgoing emails | Supported |
| Send auto-acknowledge/auto-reply emails to senders |
| Supported | Supported | |||
| Generating From address and Sender name from fields or custom fields | Supported | Supported | ||
Sending predefined responses (manually generated responses, not Confluence content pasted) | Supported | Supported | ||
| Distribution lists | Supported | |||
| Execute workflow transitions based on outgoing manual emails | ||||
| Supporting CC and BCC recipients | ||||
| Incoming email options | ||||
| Mail Handlers | ||||
| POP3 / IMAP accounts handling * | ||||
Fallback to a default reporter | Supported | Supported | ||
| Process incoming emails as new issues or comments | Supported | Supported | ||
| Create or Comment Or Link mail handler based on JQL | Supported | |||
| Execute workflow transition on issues upon processing emails |
| Supported | ||
Removing previous messages from reply emails using split regex |
| Supported | Supported | |
| Field |
| Actions based on incoming emails | ||||
| Initialize issue fields from email in new or existing issues | Supported | Supported | ||
| Find issues related to incoming emails using issue fields | Supported | |||
| Email filtering |
| Supported | Supported | |||
Execute workflow transitions |
based on regular expressions | Supported | |||
| Attachment handling | ||||
| Name and size based attachment filtering | Supported | Supported | ||
| MD5 hash based attachment filtering | Supported | |||
| Configuration | ||||
| Supported | ||||
| Supported | Supported | |||
| Supported | Supported | |||
| Additional features | ||||
| Searchable audit log of emails sent or received | Supported | Supported | Supported | |
| JQL functions to search for issues sent / created or commented via emails | Supported | |||
| Using RestAPI to send emails | Supported | |||
| Multiple SMTP server support | Supported | Supported |
* Emails are always downloaded and deleted or moved from / within the email accounts by Jira's Email Puller and Email Processor.
The email puller retrieves emails from email accounts (e.g. Gmail and Yahoo Mail) and stores them in the database (Emails received before the accounts are connected to the system are not pulled in).
The email processor processes emails retrieved by the puller.
...
Disclaimer
| Note | ||
|---|---|---|
| ||
Not all features are listed here to a full extent due to minor differences in the different products and deployment versions, however, we have tried to highlight the biggest benefits one solution has over another. |
| Feature | Disclaimer |
|---|---|
POP3 / IMAP accounts handling* | The feature will be available in Q3 2019. |