Redmine Notification Plugin — The Right Alert to the Right Person at the Right Time
The Redmineflux Redmine Notification Plugin replaces Redmine's fixed notification model with configurable rules. Define exactly what triggers an alert, who receives it, and how it is delivered — without flooding inboxes with notifications nobody reads.
What Breaks When Notifications Are All or Nothing
Redmine's default notifications create two problems simultaneously. Teams subscribe to everything and stop reading notifications because volume is too high — which means critical alerts get ignored alongside routine ones. At the same time, important status changes and SLA breaches go unseen because they are buried in the noise of lower-priority updates. The wrong people receive alerts: watchers see every minor comment while stakeholders miss major escalations. There is no delivery channel flexibility — email only, regardless of whether the team checks it promptly — and no digest option for high-volume projects.
What is the Redmine Notification Plugin?
The Redmineflux Notification Plugin adds configurable, rule-based notifications to Redmine. Each notification rule defines a trigger condition (field change, status transition, SLA breach, assignment, due date), a recipient list (role, user, or external address), and a delivery channel (email, webhook, or Slack). Alerts reach the right people through the right channel — and nothing else.
Notifications That Work for Your Team, Not Against Them
The Notification Plugin enhances Redmine without replacing it. It replaces broad, noisy alert subscriptions with structured rules that reflect how your team actually works. Fewer, more relevant notifications mean better response rates on the alerts that matter. Teams that have trained themselves to ignore Redmine email because the volume is too high can recalibrate — rule-based routing means every notification that arrives is one someone defined as worth receiving.
What Your Team Gains with the Redmine Notification Plugin
Every notification rule is explicit about what triggers it, who receives it, and how it is delivered. Nothing outside those rules generates an alert, which means everything that arrives is relevant.
Escalation alerts reach the engineering lead, not the whole team. SLA breach notifications go to the support lead, not the original reporter. Recipient configuration matches how your team's accountability is actually structured.
Email, webhook, and Slack delivery allow each alert rule to use the channel most appropriate for its urgency and audience. Critical alerts go to Slack for immediate visibility; summary updates go to email for record-keeping.
High-volume projects generate dozens of low-priority updates. Digest mode batches them into a single daily or hourly summary email, which reduces inbox load without eliminating coverage of routine activity.
Notification rules are managed at the admin level. End users cannot create rules that flood other team members' inboxes. The governance model keeps alert configuration intentional and accountable.
Core Capabilities of the Redmine Notification Plugin
Define Exactly What Conditions Send an Alert
- Trigger on field change — status, priority, assignee, due date, and custom fields
- Trigger on specific status transition pairs, such as "In Progress" to "Blocked"
- Trigger on due date proximity — one day, three days, or a custom lead time before due
- Trigger on inactivity — an issue not updated within a configurable number of days
- Trigger type produces precisely the alerts the team needs without generating notifications for unrelated activity.
Route Alerts to the People Who Need to Act
- Send to specific Redmine users, roles, or groups
- Send to the issue assignee, reporter, or watchers based on their role in the specific issue
- Include external email addresses outside the Redmine user base for client or stakeholder notifications
- Conditional routing sends different recipients depending on project, tracker, or priority — which allows escalation paths to reflect actual accountability structures
Send Through the Channels Your Team Monitors
- Email delivery supports configurable subject lines and body templates per rule
- Webhook delivery integrates with internal systems or ITSM tools without requiring additional connectors
- Slack notification delivery uses an incoming webhook URL configured in the Slack workspace
- Different triggers can use different delivery channels within the same Redmine instance
Reduce Notification Volume Without Losing Coverage
- Configurable digest schedules cover hourly, twice-daily, and end-of-day options
- Digest applies per project or globally based on admin configuration
- High-priority triggers bypass digest mode and deliver immediately regardless of the digest schedule
- Digest summaries include all triggered alerts with direct links to each affected issue
Track What Was Sent and When
- A full log of all triggered notifications includes timestamp, recipient, delivery channel, and delivery status
- Delivery failure alerts surface webhook and email errors before they cause missed notifications
- Per-rule send counts and recipient engagement summaries are visible in the admin interface
- The notification log exports for compliance and SLA audit purposes
How the Notification Plugin Works with Other Redmineflux Plugins
The Notification Plugin connects the Redmineflux workflow to the channels your team monitors. Configure rules to alert the engineering lead when an issue on the Agile Board Plugin sprint board transitions to Blocked. Trigger SLA breach alerts that connect to Helpdesk Plugin ticket timers. Route timesheet approval notifications from the Timesheet Plugin to the relevant manager through the configured approval chain.
Trusted by Teams That Need Every Alert to Mean Something
What People are Saying!
Project Manager, Newyork
Project Manager
Project Manager, Singapore
Project Lead, Spain
Team Lead, Rochester, U.S.
CEO, Brazil
Project Manager
Project Manager, Moscow, Russia
Redmineflux plugins have been a game-changer for our Redmine setup. The enhanced features like advanced time tracking, custom workflows, and improved reporting have significantly boosted our productivity. The integration was seamless, and the support team was fantastic. Highly recommend these plugins to any Redmine user!
Getting all of my business data organized in one place is all I wanted. With Redmineflux, I can filter data and simplify my agile operations.
Redmineflux themes have completely transformed the look and feel of our Redmine instance. We were looking for a way to make our Redmine more visually appealing and user-friendly, and these themes delivered on both fronts. The customization options are fantastic, allowing us to tailor the design to our company’s branding.
The Redmineflux Timesheet plugin has made it so much easier for our team to track their time. The ability to easily log time for multiple tasks at once and bulk edit or delete entries is a huge time saver.
Redmineflux Gantt Chart improved visibility and Efficiency, it provides a clear view of tasks, improves communication, & streamlines workflows for faster project completion.
Redmineflux themes are not just about aesthetics; they’re designed with user experience in mind. The improved navigation and clarity have streamlined our workflows significantly. The support team was also incredibly helpful in assisting us with customization.
Highly recommend!”
Redmineflux has an easy-to-use interface & is easily customizable. It helps active coordination and focuses project resources in one direction.
The self-hosted version of Redmineflux has transformed our enterprise project management. The customization options and reliable performance have greatly improved our workflows. The support team is responsive, ensuring our needs are met. Highly recommended for organization looking to streamline project management.
Deployment Options
Self-Hosted
When deployed on your own infrastructure, your team manages server uptime, Redmine upgrades, backups, and plugin compatibility. The Notification Plugin adds rule-based alert management without changing who owns the infrastructure. Full control stays with your team.
Managed Cloud
The Notification Plugin runs within Redmineflux Managed Cloud. Infrastructure is fully managed by the Redmineflux team. Updates are automated, backups are secured, and uptime is SLA-backed. If infrastructure management is overhead your team does not need, Redmineflux Managed Cloud transfers that responsibility entirely.
Built for Teams That Need Every Alert to Mean Something
| Role | What they gain |
|---|---|
| Project Manager | Status change and deadline alerts routed to the right people without inbox overload |
| Engineering Lead | Escalation and blocking issue alerts through the channels engineers actually monitor |
| Support Lead | SLA breach and unassigned ticket alerts with immediate delivery — no digest delay |
| IT Director | Governed notification rules with full audit trail and delivery history |
Frequently Asked Questions
Yes. The Notification Plugin supports direct delivery to Slack via an incoming webhook URL that you configure in your Slack workspace. No third-party connector or middleware is required. Each notification rule can specify a different Slack webhook — allowing routing to different channels based on project or trigger type.
Yes. Notification rules are managed at the admin level by default. Project managers can be granted permission to manage rules within their own projects. End users cannot modify global or project-level rules unless that permission is explicitly granted, which maintains governance over alert configuration.
No. Individual rules can be configured to bypass digest mode and deliver immediately regardless of the digest schedule. Rules triggered by high-priority status changes, SLA breaches, or security-related transitions are typically set to immediate delivery. Digest mode applies only to rules where it is explicitly enabled.
The Redmineflux Notification Plugin is tested and maintained against the three most recent stable Redmine releases. Compatibility is verified with each plugin update. Check the plugin documentation for the confirmed supported version list before installing on your instance.
