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 not associated with new projects. However, you can associate this notification scheme with your project through the Project Summary page as described below. You can modify this scheme or if you prefer, create other notifications schemes for particular projects.
On this page:
The events which can generate email notifications are:
イベント | 説明 |
|---|---|
Issue Created: | 課題がプロジェクトに作られました。 |
Issue Updated: | 課題の詳細が変更されました。これには課題コメントの削除が含まれます。 |
Issue Assigned: | 課題が新しいユーザに割り当てられました。 |
Issue Resolved: | 課題が解決されました(通常、取り組みと修正が終わった後)。 |
Issue Closed: | An issue has been closed. (Note that an issue may be closed without being resolved; see Workflow). |
Issue Commented: | 課題にコメントが追加されました。 |
Issue Comment Edited: | 課題のコメントが編集されました。 |
Issue Reopened: | 課題が再開されました。 |
Issue Deleted: | 課題が削除されました。 |
Issue Moved: | 課題がこのプロジェクトに移動、またはこのプロジェクトから移動されました。 |
Work Logged On Issue: | 課題にログインした時間がありました(すなわち作業ログが追加されました)。 |
Work Started On Issue: | 担当者が課題で作業を開始しました。 |
Work Stopped On Issue: | 担当者が課題で作業を停止しました。 |
Issue Worklog Updated: | 課題の作業ログのエントリが編集されました。 |
Issue Worklog 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:
受信者 | 説明 |
|---|---|
現在の担当者 | 現在課題が割り当てられているユーザ。 |
報告者 | 課題を最初に作成したユーザ。 |
現在のユーザー | このイベントを開始する操作を実行したユーザ。 |
プロジェクトリード | The user who is managing the project to which the issue belongs. |
コンポーネントリード | The user who is managing the component to which the issue belongs. |
Single User | A particular user in your JIRA system. |
グループ | A particular group in your JIRA system. |
プロジェクトロール | The members of a particular project role for this project. |
Single Email Address | Any email address that you wish to alert. |
すべてのウォッチャー | 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
特定のイベントに新しい受信者を追加する方法: