A Redmine notification plugin solves a specific problem Redmine’s default email alerts are binary. Developers receive an email when assigned an issue, when a comment is added, or when a status changes. In practice, this works for small teams. However, the system has no conditions, no roles, and no in-app feed.
The result is notification noise or missed alerts. A user either receives all notifications for a project, or none. There is no way to subscribe only to high-priority issues, to alert only when an overdue issue passes its deadline, or to notify a specific role when a blocker is created. Consequently, many team members opt out of email notifications entirely and miss updates that matter.
The Redmineflux Notification Plugin replaces this binary approach with configurable alert rules. Specifically, the plugin sends notifications based on conditions: issue priority, status change, assignment, due date proximity, or custom field values. In-app notifications keep team members informed inside Redmine without relying entirely on email.
The short answer: Redmine sends email notifications based on user subscription settings watchers, assignees, and project members with notification preferences enabled receive emails for issue updates. There are no condition-based rules, no in-app notification feed, and no role-specific alert routing. The Redmineflux Notification Plugin adds configurable rules, in-app alerts, overdue notifications, and priority-based routing so the right people get notified for the right reasons.
In short, default Redmine email notifications are configurable per user from the account settings. Users choose whether to receive notifications for all events on watched issues, only for changes where they are mentioned, or not at all. Administrators cannot configure team-wide rules based on issue conditions only individual users can adjust their own preferences.
The Redmineflux In-App Notification Plugin adds a rule engine for notifications. Administrators define rules at the project level, and the plugin triggers notifications based on conditions:
Specifically, rules target roles, individual users, or all members with a particular permission. Notifications are precise rather than broadcast the right person gets the right alert, not everyone gets everything.
Configure smarter notifications and keep every project update under control. Explore the Notification Plugin.
The plugin adds a notification feed inside the Redmine interface accessible from the top navigation bar on every page. In practice, team members see their unread notifications without switching to email.
For development teams where Redmine is the primary work interface, in-app notifications keep awareness inside the tool. A developer working in Redmine sees a new assignment notification the moment it arrives without needing to check email or be interrupted by an email client.
The notification feed shows the issue title, the type of change, the user who made the change, and a direct link to the issue. Additionally, the feed marks notifications as read when the issue is opened no manual clearing required.
The plugin adds automated overdue issue notifications. When an issue passes its due date without being closed, the plugin sends configurable notifications to the assignee, the project manager, or both at intervals the rule defines (immediately at overdue, again after 24 hours, again after 48 hours).
In contrast, native Redmine shows overdue issues in reports but generates no proactive alert. As a result, project managers must run a daily overdue report to catch slipping issues the plugin removes that manual step.
Notifications route by role rather than by individual user. When a blocker issue is created in a project, the rule notifies all users with the “Project Manager” role. When an issue moves to “Deployed to Production,” all users with the “QA Lead” role receive the alert.
Consequently, notification rules do not need updating when team members change. The rule targets the role whoever holds it receives the notification. For example, onboarding a new QA Lead automatically puts them into existing notification rules with no reconfiguration.
For team members who prefer fewer emails, the plugin supports a digest mode. Instead of one email per notification, users receive a single digest email at a configured interval hourly or daily summarising all notifications since the last digest.
In practice, digest mode reduces email volume without turning off notifications entirely. Similarly, team members stay informed without managing a high-volume inbox useful for senior stakeholders who need awareness but not real-time interruptions.
Before configuring rules, identify the events your team actually needs alerts for. In practice, common high-value events are: new Critical priority issue created, issue overdue, status changed to “Blocked,” issue assigned to a new person. Events that generate noise every comment on every issue should be excluded from the outset.
Open the Notification Plugin settings for a project and create rules for each notification event. For each rule: set the trigger condition, the target (role, user, or all members), the delivery method (in-app, email, or both), and optionally a delay (immediately, after 1 hour, daily digest).
Specifically, start with fewer rules and add more based on what the team actually acts on. Notification systems that send too many alerts quickly become ignored fewer, precise alerts outperform broad coverage.
Individual team members configure their own notification preferences within the rules the administrator has set. A developer who prefers in-app notifications over email can disable email delivery for most rules while keeping in-app alerts active. A project manager who needs immediate email for overdue issues can keep that rule on email delivery.
Additionally, user preferences respect the administrator’s rules users choose between delivery methods but cannot opt out of rules marked as mandatory. This balance keeps critical alerts enforced while giving individuals control over everything else.
The Notification Plugin integrates with the Agile Board Plugin and Custom Dashboard Plugin. When a notification rule triggers for an issue on the sprint board, the in-app notification links directly to that board card. Similarly, a project manager reviewing the Custom Dashboard who receives an overdue notification can navigate directly to the overdue issue from the feed without leaving the dashboard view.
As a result, the notification system stays inside Redmine’s existing navigation rather than requiring context switches to external tools. In short, alerts surface where the team already works.
Run Redmine with intelligent notifications and all essential plugins pre-installed. Explore Managed Cloud.
Redmine’s default email notifications are configured per user in account settings. For condition-based rules notifying specific roles when specific events occur the Redmineflux Notification Plugin adds a rule engine at the project level. Rules target specific trigger conditions, roles, and delivery methods without requiring users to self-configure.
Yes. The Notification Plugin configures rules at the project level. Different projects can have different notification rules. A high-urgency client project can have more aggressive overdue notification rules than an internal documentation project.
Not natively. Redmine sends email notifications only. The Redmineflux In-App Notification Plugin adds a notification feed inside the Redmine interface accessible from the top navigation bar so team members see updates without switching to email.
Yes. The Notification Plugin adds automated overdue notifications. When an issue passes its due date without being closed, the rule sends notifications to the assignee and project manager at configured intervals. Native Redmine shows overdue issues in reports but does not send proactive alerts.
The Redmineflux In-App Notification Plugin supports Redmine 5.0.x, 5.1.x, and 6.0.x. Teams running Redmine 4.x should contact support before purchasing to confirm compatibility.
Notifications that reach the wrong people at the wrong time become noise. In contrast, notifications that do not reach the right person become missed deadlines. The Redmineflux Notification Plugin gives your team control to set up alerts that are specific enough to act on and quiet enough to stay enabled. Consequently, the alerts that matter stay on, and the ones that don’t get filtered before they create noise.
See how rule-based alerts and in-app notifications improve team communication in Redmine. Book a Free Demo.
