Documentation for JIRA 4.4. Documentation for other versions of JIRA is available too.
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.
Your JIRA system contains a notification scheme called 'Default Notification Scheme', which by default is associated with all newly-created projects. You can modify this scheme, and also create other schemes for particular projects if you wish.
On this page:
The events which can generate email notifications are:
Event | Description |
---|---|
Issue Created: | An issue has been entered into the system. |
Issue Updated: | An issue has had its details changed. This includes the deletion of an issue comment. |
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 Workflow). |
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 or out of 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. |
The exact nature of these events depends on the workflow transition(s) from which they were fired. |
JIRA does not have a specific notification event for the deletion of issue comments. When an issue's comment is deleted, JIRA sends out an email notification as an 'Issue Updated' event.
The recipients who can receive email notifications are:
Recipient | Description |
---|---|
Current Assignee | The user to whom the issue is currently assigned. |
Reporter | The user who originally created the issue. |
Current User | The user who performed the action that has triggered this event. |
Project Lead | The user who is managing the project to which the issue belongs. |
Component Lead | The user who is managing the component to which the issue belongs. |
Single User | A particular user in your JIRA system. |
Group | A particular group in your JIRA system. |
Project Role | The members of a particular project role for this project. |
Single Email Address | Any email address that you wish to alert. |
All Watchers | All users who are watching the issue. |
User Custom Field Value | The value of a custom field of type User Picker or Multi User Picker that may have been associated with issues. |
Group Custom Field Value | The value of a custom field of type Group Picker or Multi Group Picker that may have been associated with issues.. |
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).
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 behaviour to be re-instated, for those customers who liked the old behaviour.
See http://jira.atlassian.com/browse/JRA-6344 for more details
To add a new recipient for a particular event: