Notification Templates define templates used in your Notification Schemes and are reusable messages you can send in reaction to SLA Events. Each Template is assigned to a selected Provider. In order to add a template to a scheme, you have to create a Notification Provider and enable it.
Each template enables you to select many message options. These options are fully customizable as you can choose the provider, name, description, issue key and subject of the message. For example, you are able to create an “SLA critical” message the content of which depends on you.
Creating a Notification Template:
Log in as a user with the Jira Administrators global permission.
Choose the cog icon> Add-ons. Select SLA PowerBox > Notification Templates to open the SLA Notification Templates page.
Tip: Keyboard shortcut: g + g + start typing notification templates...- Click the Add Template button.
- Enter a Name and a short Description of the notification template.
- Fill in all the necessary fields. They are described in the Configuration fields section at the bottom of the page.
- Your message can be previewed when selecting the Show message preview option.
- Click the Create button to create the notification scheme.
| Info | ||
|---|---|---|
| ||
Your message template view depends on the notification provider selected before. The Provider has to be enabled if you want to assign it to a template. |
Editing a Notification Template:
- Log in as a user with the Jira Administrators global permission.
- Choose the cog icon> Add-ons. Select SLA PowerBox > Notification Templates to open the SLA Notification Schemes page.
Tip: Keyboard shortcut: g + g + start typing notification templates... - Select Edit in the Operations section.
- Edit the Name for the notification and/or the Description and/or other fields..
- Confirm with the Save button.
| Info | ||
|---|---|---|
| ||
If a Provider has been disabled, it will not be available on the list in the Edit Notification Template view. |
Deleting a Notification Template:
- Log in as a user with the Jira Administrators global permission.
- Choose the cog icon> Add-ons. Select SLA PowerBox > Notification Templates to open the SLA Notification Schemes page.
Tip: Keyboard shortcut: g + g + start typing notification templates... - Select Delete in the Operations section.
- Confirm with the Delete button.
| Note | ||
|---|---|---|
| ||
Templates already assigned to a Notification Scheme cannot be deleted. |
Configuration Fields:
Name - It allows you to identify your notification.
Description - A short description of your notification.
Notification Provider - It allows you to choose a provider (added in the Notification Providers tab).
Subject - The subject of your notification. This will be visible in the recipient's mailbox.
Email format - Text/plain means that the email will be composed of a plain text, without any formatting. Text/html allows to add the HTML formatting.
Message - Enter the text of your notification here. You can add numerous variables (tags) that will be uploaded automatically from Jira. You can use these to configure each message content to show different pieces of information extracted from the selected issue, e.g. to control the issue resolution time, the current logged in user or the original time estimate.
| Info | ||
|---|---|---|
| ||
To view the list of tags, click on the |
This allows you to highlight the most important points of your message, which is useful if you want to draw recipient’s attention to specific pieces of information instantly.
Issue Key - If you add tags to the message, you can preview them using data from a sample issue. To do that, enter a sample issue key (e.g. "SD-11") into the Issue Key field.
SLA field - Select a SLA field that will be shown in the notification preview.
Show message preview - It allows to preview the notification in a separate window.
Calendar - Select a calendar if you want this message to be sent only at specific times (e.g. working hours).
Additional JQL - An additional JQL condition allows you to send the notification for specific issues only so that the number of issue matches is reduced. It is particularly useful when e.g. your issue is critical.