JETI vs. JIRA Comparison
The below table is to compare the mailing capabilities of Jira and Email this Issue (both Server and Cloud versions).
Feature | Jira out-of-the-box | Jira Service Desk | Email This Issue CLOUD | Email This Issue SERVER |
|---|---|---|---|---|
|
|
|
|
|
Outgoing Email Options |
|
|
|
|
Custom email templates | Not Supported | Supported | ||
Notifications |
|
|
|
|
Support for single email addresses stored in custom fields via event notifications | Not Supported | Not Supported | Supported | Supported |
Event notifications in Notification schemes | Supported | Supported | ||
Event notifications with JQL conditions | Not Supported | Supported | ||
Manual Email Defaults |
|
|
|
|
Manual email options editing | Not Supported | Not Supported | Supported | |
Send issue details to users and to external email addresses (Email button) | Not Supported | Not Supported | ||
Miscellaneous |
|
|
|
|
Send emails from a workflow transitions | Not Supported | Supported | ||
Deleting SMTP prefix from outgoing emails | Not Supported | Not Supported | Supported | |
Send auto-acknowledge/auto-reply emails to senders | Not Supported | Not Supported | ||
Generating From address and Sender name from fields or custom fields | Not Supported | Not Supported | ||
Sending predefined responses (manually generated responses, not Confluence content pasted) | Not Supported | Not Supported | ||
Distribution lists | Not Supported | Not Supported | Not Supported | |
Execute workflow transitions based on outgoing manual emails | Not Supported | Not Supported | Not Supported | |
Supporting CC and BCC recipients | Not Supported | Not Supported | Supported | |
Incoming email options |
|
|
|
|
Mail Handlers |
|
|
|
|
POP3 / IMAP accounts handling * | Supported | Supported | Supported | Supported |
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 | Not Supported | Not Supported | Not Supported | |
Execute workflow transition on issues upon processing emails | Not Supported | Supported | ||
Removing previous messages from reply emails using split regex | Supported (limited) | Supported (limited) | ||
Field Actions based on incoming emails |
|
|
|
|
Initialize issue fields from email in new or existing issues | Not Supported | Not Supported | ||
Find issues related to incoming emails using issue fields | Not Supported | Not Supported | Not Supported | |
Email filtering | Not Supported | Not Supported | ||
Execute workflow transitions based on regular expressions | Not Supported | Not Supported | Not Supported | |
Attachment handling |
|
|
|
|
Name and size based attachment filtering | Not Supported | Not Supported | ||
MD5 hash based attachment filtering | Not Supported | Not Supported | Not Supported | |
Configuration |
|
|
|
|
Sender blacklist | Not Supported | Not Supported | Not Supported | |
Recipient whitelist | Not Supported | Not Supported | ||
Recipient blacklist | Not Supported | Not Supported | ||
Additional features |
|
|
|
|
Searchable audit log of emails sent or received | Not Supported | Supported | ||
JQL functions to search for issues sent / created or commented via emails | Not Supported | Not Supported | Not Supported | |
Using RestAPI to send emails | Not Supported | Not Supported | Not Supported | |
Multiple SMTP server support | Not Supported | Not Supported | Supported |
Disclaimer
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. |