| Redirect | ||||||
|---|---|---|---|---|---|---|
|
| Note | ||
|---|---|---|
| ||
Thank you for visiting our old product documentation site. Note that weare in the process of migrating our product documentation and soon we will notno longer store or update our documentation here.Please navigate to our new documentation site and update your bookmarks accordingly. If you're looking for the former content of this page, click here. |
| Table of Contents |
|---|
Email This Issue contains a powerful workflow post function to send fully customizable emails as part of the workflow transitions. Sending emails from transitions may be a better alternative to event notifications. As specific operations (e.g. Request Approved) may not be precisely represented by generic event types like Issue Updated.
The list of currently added post functions is available from the Emails / Workflow Post Functions menu.
Add a Post Function to the Workflow
The email post functions must be added or edited in the workflow editor in JIRA.
It is perfectly valid to add multiple Email This Issue post functions to the same transition, they will be called one after the other.
It is important to note that the post functions must be moved down before or after the function firing the event. This is needed because Email This Issue expects the issue to be updated and fully indexed before rendering issue fields in the email.
Post Function Details
The post function details include the following:
- WHEN or JQL criteria
- WHO or recipients.
- WHAT or content settings
JQL
...
, |
...
The below example will make sure that emails will be sent only when the issue is of Highest priority.
To enter a JQL which involves a user name (such as defining the assignee of an issue), follow the below steps:
...
click |
...
Recipients
Recipients selected in the post function will receive the emails.
Emails may have To, Cc and Bcc recipients. For all of these recipient types you can enter or select:
- 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
Content Settings
Content settings in Email This Issue Post Functions specify the email template to use, and additional content that will be added to the email.
Content Settings attributes include:
...
...
...
...
here |
...
The template's $!mailSubject variable renders the entered value in the email subject
...
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
...
The value selected in this field determines which issue attachments should be attached to the email.
Options are:
...
. |
...
Additionally, you can configure the policy to filter internal attachments. When this option is enabled and the issue is in a Service Management project, then the attachments that were added via internal comments will not be included in the email.
...