.png%3Falt%3Dmedia%26token%3D303d21c4-bfd2-4778-a50a-1bb043b0732e){kind=icon}
.png%3Falt%3Dmedia%26token%3D303d21c4-bfd2-4778-a50a-1bb043b0732e){kind=icon}
Comparing Email This Issue and Jira Server/DC
The following table is a comparison of email sending capabilities of Jira Server/DC and Email This Issue for Jira Server/DC.
Feature | Email This Issue | Jira Core / Software | Jira Service Management |
|---|---|---|---|
 | | | |
|  | Limited only to customer notifications | |
Conditional event notifications | |  | |
Send link to issues to users and email addresses (Share button) | | | |
| | | |
Bulk email sending (send multiple issues in one email) | | | |
Email batching for notifications | | | |
| | | |
Send email via automation | | Possible using Jira Automation | |
Process incoming emails as new issues or comments | | | |
| | | |
Find issues related to incoming emails using issue fields | | | |
Create or Comment Or Link mail handler based on JQL | | | |
Create Or Comment Or Subtask based on JQL | | | |
| | Possible, using automation | |
Send auto-reply emails back to senders | | | Limited, can be achieved using
Jira out-of-the-box automation |
Blocklist of senders to block emails | | | |
MD5 hash based attachment filtering | | | |
Support for external issue participants via event notifications | | | |
From address and sender name in outgoing emails generated from fields or custom fields | | | |
| | | |
| | | |
OAuth 2.0 support for Google and Microsoft accounts | | | |
Custom/removable prefix for outgoing emails | | | |
Multiple SMTP Connections | | | |
Webhook-based alerting for email incidents | | | |
Last modified 1yr ago