Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

...

The Events and Filters of an Email Notification determine when emails must be sent out for an issue. 

Status
colourGreen
titleWhen
 may be defined by the following fields:

FieldValueExplanation
EventsEvent types selected. Mandatory.This field selects the Jira event types upon which the Email Notification rule will send emails
.Suppress notification
.
Event's triggercreated events
  • In Jira web interface/Customer portal
  • By mail handler
If there is an issue created event in the events list, then you can decide when you want to listen on these events.
commented events
  • Jira web interface
  • manual email
  • Mail hanlder
If there is a comment related event (eg. Issue commented, Service Desk Public Comment added, ...) in the events list, then you can decide when you want to listen on these events.
JQL Filter
Valid JQL query. Optional.This is a filter. If specified, issues must match the criteria otherwise the Email Notification rule is ignored and emails not sent
Fields
Issue fields or custom fields selected. Optional

If specified, Email This Issue will send emails only of the selected fields have been modified in the issue during the operation that resulted in the event.

Example: 

Image RemovedImage Added

This Email Notification rule will be applied if Issue Updated or Issue Commented or Issue Moved events are fired AND the issue is of priority Highest AND attachments are added during the operation.

...

  • users from Jira
  • email addresses
  • Persons related to the issue or project: Assignee, Reporter, Watchers, Project Lead, Current User
  • Project Roles
  • User Groups
  • Custom Fields that may hold email addresses or users or groups

Image RemovedImage Added

The available user groups, project roles and custom fields may be limited in the Recipient Restrictions. This is useful for example if you want to avoid users accidentally selecting "jira-users" group as a recipient and hence to send emails to all users.

...

FieldValueExplanation
TemplateAn Email This Issue TemplateThe template selected here will be used to render the subject and body of the final email.
SubjectText to be added to the email subject

Text entered here will be combined into the final email's subject using the template above.

The template's $!mailSubject variable renders the entered value in the email subject

MessageText to be added to the email body

Text entered here will be combined into the final email's Body using the template above.

The template's $!mailBody variable renders the entered value in the email body

AttachmentsAttachment policy

The value selected in this field determines which issue attachments should be attached to the email.

Options are:

  • all: all attachments added
  • none: none of the attachments added
  • added in the last operation: attachments added as part of the operation that fired the event (e.g. Edit Issue)
  • newest versions of all: newest version of all attachments. Attachments having the same name are considered versions of the same attachment.
  • added recently: latest added attachments (Actually since we don't get any list about the added attachments, we have to figure out the latest added attachment. For this we ask for all the attachments of the issue and send only added in the last minute from the latest one.)
Email FormatHTML or TEXTThe format of the emil to send.

...