JETI vs. JIRA Comparison

Emailing basics

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.
Downloaded emails are then passed on to JETI which creates new issues from the emails or adds new comments to already existing issues based on the emails.

The below table is to compare the mailing capabilities of Jira and Email this Issue (both Server and Cloud versions).

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.
Linked features contain links referring to the server version documentation of JETI. For the Cloud version's documentation, please refer to the Cloud documentation overview.

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
Notifications
Support for single email addresses stored in custom fields via event notifications
Event notifications in Notification schemes
Event notifications with JQL conditions
Manual Email Defaults
Manual email options editing
Send issue details to users and to external email addresses (Email button)
Miscellaneous
Send emails from a workflow transitions
SMTP prefix editing
Send auto-acknowledge emails to senders
Send *link to issues* to users and email addresses (Share button)
Generating From address and Sender name from fields or custom fields
Sending predefined responses (manually generated responses, not Confluence content pasted)
Distribution lists
Incoming email options
Mail Handlers
Fallback to a default reporter
Create Or Comment Or Subtask based on JQL
Process incoming emails as new issues or comments
Create or Comment Or Link mail handler based on JQL
Execute workflow transition on issues upon processing emails
Removing previous messages from reply emails using split regex
Field Rules
Initialize issue fields from email in new or existing issues
Find issues related to incoming emails using issue fields
Email filtering using field rules
Execute workflow transitions using field rules
Attachment handling
Name and size based attachment filtering
MD5 hash based attachment filtering
Configuration
Sender blacklist
Recipient whitelist
Recipient blacklist
Additional features
Searchable audit log of emails sent or received
JQL functions to search for issues sent / created or commented via emails