Redmine

Add detailed options for issue update notifications¶

This patch extends the notification settings to allow more granular control over issue update notifications.
Currently, issue update notifications allow selecting only a small predefined subset of change types (for example status, assignee, priority, notes, attachements, or target version). Other attribute changes, relations, and custom fields cannot be configured individually.
With this change, administrators can configure notifications more precisely by selecting which kinds of changes and, optionally, which specific fields should trigger notifications.

Overview¶

The following new notification events are introduced as children of Issue updated:

• Issue attributes updated
• Issue relations updated
• Issue custom fields updated

Each of these events can be configured independently.
If a notification event checkbox is enabled, notifications are sent for all changes of that type.
If the checkbox is disabled, notifications are only sent when specific fields are selected in the corresponding multiselect.

Removed notification events¶

The following notification events have been removed:

• issue_status_updated
• issue_assigned_to_updated
• issue_priority_updated
• issue_fixed_version_updated

These events are now covered by the more general Issue attributes updated notification in combination with its detailed field selection.
Using the new detail multiselect, administrators can explicitly select the corresponding attributes (such as status, assignee, priority, or target version), which provides the same functionality in a more flexible and consistent way.

Notifications for notes and attachments (issue_note_added and issue_attachment_added) are unchanged and continue to be handled as separate events.

Notification behavior¶

If a notification event checkbox is enabled, all changes of that type trigger notifications.
If the checkbox is disabled but specific fields are selected, notifications are triggered only for those fields.
If neither the checkbox nor any field is selected, no notifications are sent for that type.
This keeps the behavior backward-compatible while enabling fine-grained filtering.

Settings UI¶

The following screenshot shows the extended notification settings in
Administration → Settings → Notifications after applying this patch:

Technical summary¶

• New notification events were added to Redmine::Notifiable .
• Detailed filtering is implemented using the set of safe issue attributes ( Issue.new.safe_attribute_names ), the predefined relation types ( IssueRelation::TYPES ), and available issue custom fields ( IssueCustomField )
• Settings are stored using separate Setting keys for each event’s detail selection.

Patches¶

The changes are provided as a series of three patches:

• Core logic for detailed issue update notifications
• Localization for new settings and delete old settings
• Tests for notification logic and settings UI

This patch addresses several standing requests for more granular issue update notifications (see #9761, #16098, #17289, #18209, #32183, #36265) by providing a unified and configurable solution.