Notification triggers
Redmine defines a fixed set of notifiable events. Each event corresponds to a specific action in the application:Issue events
Issue events
| Event | Description |
|---|---|
issue_added | A new issue is created in a project |
issue_updated | An issue is updated (parent event for the sub-events below) |
issue_note_added | A comment (journal note) is added to an issue |
issue_status_updated | The status of an issue changes |
issue_assigned_to_updated | The assignee of an issue changes |
issue_priority_updated | The priority of an issue changes |
issue_fixed_version_updated | The target version of an issue changes |
issue_attachment_added | A file is attached to an issue |
News and document events
News and document events
| Event | Description |
|---|---|
news_added | A new news item is published in a project |
news_comment_added | A comment is posted on a news item |
document_added | A new document is added to a project |
file_added | A file is added to a project or version |
Wiki and forum events
Wiki and forum events
| Event | Description |
|---|---|
wiki_content_added | A new wiki page is created |
wiki_content_updated | An existing wiki page is edited |
message_posted | A new forum message or reply is posted |
Who receives notifications
For each event, Redmine builds a recipient list by combining several groups of users:Notified users
Project members whose notification preferences match the event. Determined by the
notified_users method on the watchable object.Watchers
Users and groups explicitly watching the item. See Watchers.
Mentioned users
Users mentioned with
@username in issue descriptions or journal notes (notified_mentions).Assignee
The user or group assigned to the issue, depending on their notification preferences.
Email notification format
Issue notification subjects follow this pattern:X-Redmine-* headers such as:
X-Redmine-Project— the project identifierX-Redmine-Issue-Id— the issue IDX-Redmine-Issue-Tracker— the tracker nameX-Redmine-Issue-Author— the login of the issue authorX-Redmine-Issue-Assignee— the login of the current assignee
Configuring your notification preferences
You can configure how many notifications you receive from My account.Notification options
| Option | Key | Description |
|---|---|---|
| For any event on all my projects | all | Receive notifications for every notifiable event across all your projects. |
| For any event on the selected projects only | selected | Receive notifications only for projects where you have enabled notifications in your membership settings. |
| Only for things I am involved in | only_my_events | Receive notifications for issues you created or are assigned to, on projects you select. |
| Only for things I am assigned to | only_assigned | Receive notifications only when you are (or were) assigned to the issue. |
| Only for things I am the owner of | only_owner | Receive notifications only for issues you created. |
| Only for things I watch | only_my_watches | Receive notifications only for items you are explicitly watching. Requires you to manually watch each item. |
| No events | none | Disable all email notifications. You will not receive any notification emails. |
Notification for high-priority issues
You can opt in to receive notifications for high-priority issues regardless of your other settings. Enable the Notify about high priority issues preference in your account settings (notify_about_high_priority_issues).
Project-level notification settings
When your account notification preference is set to For any event on the selected projects only (selected), you control which projects send you notifications from within each project’s membership settings.
The
mail_notification flag is stored on your project membership record. When Redmine builds the notified users list for an issue in that project, it queries memberships.select { |m| m.mail_notification? } to collect the set of project IDs for which you have opted in.
Notification delivery
Redmine delivers emails asynchronously usingdeliver_later, which queues emails through the Active Job backend configured by your administrator. Each recipient receives an individually addressed email rendered in their preferred language.
The language used for each notification is determined by the recipient’s account language setting, falling back to the application’s default language when the recipient’s language is not configured.
Redmine does not currently support digest emails. Each event generates individual emails sent immediately (or via the job queue) to all matching recipients.