Advanced email configuration
Last updated
Was this helpful?
Last updated
Was this helpful?
Advanced email configurations provide a set of optional features that can be useful with more complex scenarios.
1. To see the list of the list of advanced email configurations, go to the Outgoing Mails configuration tab and select Advanced Email Configuration under GENERAL CONFIGURATION.
2. Add a new configuration by clicking on the Add button.
3. Edit existing ones by clicking on the three dots and choosing Edit.
The scope determines to which issues this setting is applicable. If there are multiple manual email configurations in the system, Email This Issue evaluates all of them and determines the one with the best matching scope for the issue.
The scope can consist of:
0 or more projects
0 or more issue types
An optional JQL query
An email trigger
To enter a JQL which involves a user name (such as defining the assignee of an issue), follow these steps:
Under the JQL Filter field, click Edit.
Enter the JQL.
When it comes to entering a user name, do the following:
Click Insert user.
Search for the user name, then click on Insert to insert a string.
Click Save to use the JQL or Cancel to delete it.
In the Email Settings tab, the following advanced attributes are available:
Field
Value
Definition
Store non-Jira Recipients
Text custom field
Select a Text custom field here to store external email addresses of each outgoing email separated with commas.
Use this field in email notification schemes to send automated emails. This way the field selected here may be considered as a field for external watchers.
Store User Recipients
Multi User Picker custom field
Select a Multi User Picker field here to store Jira user recipients of each outgoing email sent in the scope of this Advanced Email Configuration
Store first sent email time
Date Time Picker custom field
Select a Date Time Picker field here to store the first sent email's sent time.
First sent email's sent time is determined by the email audit log. This means that the value will always be the sent time of the first email, not the first emails sent after this field has been set.
From Name Pattern
Velocity-enabled name pattern
This pattern allows to dynamically generate From Name attribute in the outgoing emails.
An example: $!issue.project.name Hotline renders the From name based on the issue's project name and will append the word "Hotline".
From Email Address Pattern
Velocity-enabled email address pattern
A pattern that evaluates to a valid email address and is used as from address in the email.
Use this field to dynamically generate the From Email Address of the outgoing emails.
Reply-To Email Address Pattern
Velocity-enabled email address pattern
A pattern that evaluates to a valid email address and is used as reply-to address in the email.
Use this field to dynamically generate the Reply-To Email Address of the outgoing emails.
BCC Address
Valid email address
Email address entered here receives all outgoing emails sent via Email This Issue.
Embedding policy: Configure how to send out attachments. It has the following options:
Embed if attachment belongs to this Jira: selecting this option will cause that all attachments (images and non-images) will be sent as part of the email.
Do not embed images at all: If you select this option, then links in the email will not be loaded, and target attachments will not be sent.
Add Bulk header: Configure whether to add the "Precedence:" bulk header to outgoing emails. It is a good practice to add this header to the emails, so that auto responds (e.g. out of office replies) aren't sent in reply to these emails.
Add auto-generated header: Configure whether to add the "Auto-Submitted:" auto-generated header to the emails. This header indicates that the message was originated by an automatic process.
Use default SMTP: Email This Issue can be configured with multiple . Select the one to use to send emails, or enable "Use default SMTP" to always use the SMTP server marked as default.
Override this setting as described in on the page
