Documentation for JIRA 4.1. Documentation for other versions of JIRA is available too.

Skip to end of metadata
Go to start of metadata

JIRA can generate email notifications for various events that happen during the issue lifecycle. Notifications are defined within a notification scheme (see below), which associates particular events with particular email recipients. The notification scheme is then assigned to a particular project; note that you can use the same notification scheme for more than one project.

The events which can generate email notifications are:

Issue Created:

An issue has been entered into the system.

Issue Updated:

An issue has had its details changed.

Issue Assigned:

An issue has been assigned to a new user.

Issue Resolved:

An issue has been resolved (usually after being worked on and fixed).

Issue Closed:

An issue has been closed. (Note that an issue may be closed without being resolved; see Statuses).

Issue Commented:

An issue has had a comment added to it.

Issue Comment Edited:

An issue's comment has been modified.

Issue Reopened:

An issue has been re-opened.

Issue Deleted:

An issue has been deleted.

Issue Moved:

An issue has been moved into this project.

Work Logged On Issue:

An issue has had hours logged against it (i.e. a worklog has been added).

Work Started On Issue:

The Assignee has started working on an issue.

Work Stopped On Issue:

The Assignee has stopped working on an issue.

Issue Worklog Updated:

An entry in an issue's worklog has been modified.

Issue Worklog Deleted:

An entry in an issue's worklog has been deleted.

Generic Event:

The exact nature of this event depends on the workflow transition(s) from it was fired.

Custom Event(s) :

The exact nature of these events depends on the workflow transition(s) from which they were fired.

Note that email notifications will only be sent to people who have permission to view the relevant issue - that is, people who:

Also note that JIRA can only send email notifications if SMTP email has been enabled (see Email Overview).

Icon

JIRA will send notification emails to both the previous assignee and the current assignee, whenever the assignee field changes.
However past versions of JIRA only sent a notification email to the previous assignee IF the operation that changed the event was the "Assign Issue" operation. It did not send a notification if the issue was edited in some other way.
The "jira.assignee.change.is.sent.to.both.parties" application property allows the old behavior to be re-instated, for those customers who liked the old behavior.

See http://jira.atlassian.com/browse/JRA-6344 for more details

Creating a Notification Scheme

  1. Log in as a user with the 'JIRA Administrators' global permission.
  2. Bring up the administration page by clicking either the 'Administration' link on the top bar or the title of the Administration box on the dashboard.
  3. On the panel on the left, under the title 'Schemes, click the link labelled 'Notification Schemes'.
  4. This will display the 'Notification Schemes' page. This page lists all of the notification schemes that JIRA currently has. Click the 'Add Notification Scheme' link.
  5. In the 'Add Notification Scheme' form, enter a name for the notification scheme, and a short description of the scheme. Click the 'Add' button.
  6. You are then shown the 'Edit Notifications' page. This page lists all of the above mentioned issue life cycle events, along with whom should be notified. It is currently empty.
  7. Click the 'Add' link in the appropriate life cycle event row.
  8. This will display the 'Add New Notification' page. Here you can choose who to notify, from the list of alternatives.

    Where:
    • Current Assignee is the user assigned to the issue.
    • Current Reporter is the user who originally created the issue
    • Current User is the user who performed the action triggering the event in question.
    • Single Email Address is any email address that you wish to alert.
      Icon

      A Single Email Address notification will only be sent if the issue is publicly viewable (as the email address of a non-JIRA user could be specified, in which case a security check is not possible). Publicly viewable issues are issues which have a Permission scheme that gives the 'Browse Projects' permission to 'Anyone' (any non-logged-in users).

    • User Custom Field Value is any custom field value of type User Picker or Multi User Picker that may have been associated with issues. An example of where this can be useful, you have a custom User field called Tester, you have the tester notified when an issue is resolved.
    • (the rest are hopefully self-evident) Note that project roles are useful for defining specific team members for each project. Referencing project roles (rather than groups) in your notifications can help you minimise the number of notification schemes in your system.
  9. After selecting the appropriate option, and filling in any required information for that option, click the 'Add' button.
  10. You will be taken back to the 'Edit Notifications' page, with the notification you just specified now listed against the appropriate issue life cycle event.
  11. Repeat steps 7 through 11 until you have specified all the notifications you want to happen.
  12. If you make a mistake, or you would like to remove who is being notified, simply do so by clicking the 'delete' link beside the person/group/role.

Assigning a Notification Scheme to a Project

  1. Log in as a user with the 'JIRA Administrators' global permission.
  2. Bring up the administration page by clicking either the 'Administration' link on the top bar or the title of the Administration box on the dashboard.
  3. A list of projects is displayed
  4. Select the project you want by clicking on the project name. This will display the project details
  5. Click the 'Select' link beside the Notification Scheme caption.
  6. This will bring up a list of notification schemes. Select the notification scheme that you want to associate with this project.
  7. Click the 'Associate' button to associate the project with the notification scheme.