Raley Emails Notifications VS Jira cloud notifications
This table compares email notification capabilities of Jira/JSM Cloud and Raley Emails Notifications.
Feature | Jira Cloud | Raley Emails Notifications |
|---|---|---|
Customisable email templates | Limited to predefined template variables and CSS | Fully customisable |
Conditional notifications with JQL Condition | Yes, with Automation | Yes |
Jira/JSM ticket attachments sending | No | Yes, inline (photos, videos) and regular attachment files |
Display value of any Custom field in body and subject of an email | No | Yes |
Display value of any JSM Asset field in body and subject of an email | Yes, in email Body | Yes |
Showing request history in customer notifications | No | Yes |
Company logo(s) in email | No | Yes |
Complex conditional notification within email template | No | Yes, with Velocity expressions |
Canned emailing from ticket | Yes, with limited fields | Yes, with all fields |
Sending to emails from a custom field value | Yes, with Automation to Company-manager projects | Yes in any project |
Sending to email(s) from JSM Assets field | Yes to single email in Email-type field | Yes to any type of field |
Approve/Decline buttons for approving of JSM requests | Yes | Yes |
Support for any email headers | No | Yes |
Sending to internal users emails | Yes | Yes |
Sending to external users emails | Yes, with Automation | Yes |
Send email on workflow transition | Yes, with Automation | Yes |
Custom from address and from name | No | Yes, including dynamic conditional from address and name |
Full support for CC and BCC recipients | No | Yes |
Audit log for sent emails | Only for failed notifications | For all notifications |
Multiple SMTP outgoing mailservers | No | Yes |
Support for GMail Oauth2 | Yes | Yes |
Support for Microsoft OAuth2 | Yes | Yes |
Support for Legacy SMTP server | No | Yes |
Digested Notifications | Partially doable with Automation | Yes |
Custom notifications on project and version events to any email | No | Yes |