...
Choose "Administration/Add-ons"
Locate the plugin at the left side:
Set up your first notification
You will see the start screen of the Notification Assistant.
Click on "Add Notification"
...
Enter the values that should be valid for your notification.
The attributes
| Attribute | Description | |||||||
|---|---|---|---|---|---|---|---|---|
| Notification Name | Give your notification a descriptive name, ie. "Remind assignees 24 hours prior to due date". Can not be equal to another notification name. | |||||||
| Description | Give your notification a description to remeber the purpose of the notification. | |||||||
| Threshold to fire | You can specify a threshold for the minimum number of issues in the JQL-query result. When reached, it will trigger the notification to fire. | |||||||
| Restrict issue trigger | Restrict the number of times a specific issue should trigger a notification in reoccurring result sets. The delta between result sets will always trigger a notification. | |||||||
| JQL Expression | You can specify any JQL Expression to be the reason to fire the notification. | |||||||
| Email Template | You have to specify the email template for this notification. The email template "Default Email Template" is the default value. | |||||||
| Recipient type People | You can specify recipients with certain attributes in the result set to receive notifications. You can configure Assignee, Reporter, Watchers and Voters. | |||||||
| Recipient type Users | You can select one or more JIRA users to be the receive notifications. | |||||||
| Recipient type Groups | You can select one or more JIRA groups to be the receive notifications. | |||||||
| Recipient type Custom Field | You can choose a custom field of type "Text Field", "User Picker", "Multi User Picker" och , "Multi Group Picker" or the third party "NFeed Users" to be the recipientrecipients. The custom field of type "Text Field" needs to be populated with one or many valid comma separated email addresses for notifications to be sent. You can add custom fields in the administration menu "Issues / Fields". | |||||||
| Recipient type Email address | You can specify a specific email address one or many email addresses to be the recipient. It can even be an address not registered in JIRA. | |||||||
| Recipient type CC Email address | You can specify one or many email addresses to get a carbon copy notification email. It can even be an address not registered in JIRA. | |||||||
Trigger Configuration
| Here is were you determine when the notification should fire and in which interval.
| |||||||
Send Configuration
| Here is where you specify if you want to use an the email template and if you want to post the notification to a some more optional way of notifications.
You are able to notify a specific HipChat room.
Maybe you want to automatically post a comment to the issues found in the result set?
You are able to call a REST-API in this way. You can use placeholders in the posted data to be able to send data depending on the issues reflecting this notification.
|
Your configured notifications
You can now see your configured notifications in this screen.
You can choose to configure, copy, delete or execute them right away.
Note that notifications that is configured to use the Event trigger configuration cannot be executed right away since they are event driven.
You are able to click the "info"-button to get a detailed information about the notification:
Set up your own Email Template
...
| Info | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
The Notification Assistant supports most of the internal JIRA fields as well as custom field types such as:
|
Click on "Add Email Template"
This is the configuration screen for your email template, customise it in a way that fits your needs.
The attributes
...
| Place holder | Description |
|---|---|
| ${username} | Give you the JIRA username of the recipient. Note that this will not apply external recipients! |
| ${fullname} | Gived you the full name of the JIRA user recipient. Note that this will not apply external recipients! |
| ${summary} | Gives you the issue summary of the first issue in the email template. Handy in event mode! |
| ${key} | Gives you the issue key of the first issue in the email template. Handy in event mode! |
| ${assignee} | Gives you the issue assignee of the first issue in the email template. Handy in event mode! |
| ${issuetype} | Gives you the issue type of the first issue in the email template. Handy in event mode! |
| ${priority} | Gives you the issue priority of the first issue in the email template. Handy in event mode! |
| ${project} | Gives you the project for the issue of the first issue in the email template. Handy in event mode! |
| ${reporter} | Gives you the reporter of the first issue in the email template. Handy in event mode! |
| ${status} | Gives you the status of the first issue in the email template. Handy in event mode! |
| ${eventtype} | In event mode, you can use the event type like "updated" or "commented" in your email templates. Only available in event mode. |
| ${CFNAME} | Gives you a custom field value from a supported custom field. Replace CFNAME with the specific Custom Field Name. |
Add new fields in email template
You can simply add new fields to the email template (supports autocomplete):
Change Email display name
...
You can now see your configured email templates at the bottom of this screen.
Connect your created Email Template to your notification
Click "Configure" notification, select the Email template it should be based upon.
Select the email template and save.
Want to publish your notifications to HipChat?
Take a look at this page.