Table of Contents |
---|
...
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 sending emails to all users.
Content Settings
...
Field | Value | Explanation |
---|---|---|
Template | An Email This Issue Template | The template selected here will be used to render the subject and body of the final email. |
Subject | Text 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 |
Message | Text 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 |
Attachments | Attachment policy | 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. |
Email Format | HTML or TEXT | The format of the emil email to send. |
Additional Settings
Additional settings offers offer a few options:
- Include Own Changes: if the current user is a recipient, use this option to send her a notification regardless of her profile setting "My changes: do not notify me". If disabled, Email This Issue will respect the profile setting.
- Add current comment to email body: if enabled and a comment is available, it will be appended to the email body
...