Notifications associate events (both system and custom) to email recipients. When an event is fired and picked up, emails will be sent out. Notification types define the recipients of emails. For example, you can set them to only send emails to a specific user or all members from a given user group. You can add multiple notifications to a given event.
Jira ships with a comprehensive list of notification types (that is, the recipients) that will cover many of your needs. The following table lists all the notification types that are available and how they work:
|
Notification type |
Description |
|
Current Assignee |
This is the current assignee of the issue. |
|
Reporter |
This is the reporter of the issue (usually the person who originally created the issue). |
|
Current User |
This is the user who fired the event. |
|
Project Lead |
This is the lead of the project the issue belongs to. |
|
Component Lead |
This is the lead of the component the issue belongs to. |
|
Single User |
This states that any user that exists in Jira. |
|
Group |
This states that all users belong to the specified group. |
|
Project Role |
This states that all users belong to the specified project role. |
|
Single Email Address |
This states any email address. |
|
All Watchers |
This states that all users are watching this issue. |
|
User Custom Field Value |
This states the users specified in the user-type custom field. For example, if you have a User Picker Custom Field called Recipient, the user that's selected in the custom field will receive notifications if he/she has access to the issue. |
|
Group Custom Field Value |
This states all users that belong to the group in the group-type custom field. For example, if you have a Group Picker Custom Field called Approvers, all users from the group (with access to the issue) that are selected in the custom field will receive notifications. |
As you can see, the list includes a wide range of options from issue reporters to values contained in custom fields. Basically, anything that can be represented as a user such as Project Lead, or contains user values such as User Custom Field Value, can be chosen to receive notifications.
If a user belongs to more than one notification for a single event, Jira will make sure that only one email will be sent so that the user does not receive duplicates. For a user to receive notifications, the user must have permission to view the issue. The only exception to this is when using the single email address option (we will discuss security in Chapter 9, Securing Jira). If the user does not have permission to view the issue, Jira will not send a notification email.
We will look at how you can add notifications to events so that users can start receiving emails shortly; however, before that, you need to first take a look at the notification scheme.