Redmine Workload – the Redmine capacity planning plugin for delivery teams.
For project managers and engineering leads running multi-team delivery on Redmine.
You can’t see Monday’s load until Monday morning.
Overcommitted sprints ship late. Under-committed sprints look fine until retros. Capacity planning lives in a spreadsheet that never quite matches what Redmine says the team is doing – and by the time someone notices the overload, the deadline is already at risk.
Capacity, not opinion.
Every capacity number on the Workload view is derived from real Redmine assignments and real configured availability – not from a PM’s memory or a stale weekly spreadsheet.
Availability reads from configured working hours, holiday schemes, and approved leave. Load comes from current ticket assignments. Adjust the Gantt timeline and the load numbers update immediately. The plan matches reality because the plan is reality.
What is the Redmineflux Workload Plugin?
Redmineflux Workload is a capacity-planning plugin for Redmine. It shows committed hours per person, per sprint, against configured availability – inside the Redmine workspace your team already uses. Plan sprints with real numbers instead of guesses, and rebalance work before delivery is at risk.
See overload before it becomes a missed deadline.
Pick a shift to see what changes in the product. They play on their own – hover to pause.
See overcommitment before the sprint starts.
Workload bars surface who’s over allocation the moment you assign the 9th ticket – before the sprint is locked. Red / amber / green indicators make overload impossible to miss, even across 20-person teams. No more retro-discovering burnout.
Hours that match reality.
Availability reads from configured working hours per day, holiday schemes, and approved leave — no HR module required. No duplicate capacity config to maintain, no weekly spreadsheet drift. The numbers in Workload are the numbers.
Reschedule without an all-hands.
Drag a task on the Gantt timeline to shift its dates, or resize to change its duration. Load numbers update immediately — no meeting, no back-and-forth. Your 4pm “who has bandwidth?” discussion happens on-screen instead.
Cross-workload conflicts surface at planning.
Engineers split across workloads see all their load in one consolidated view. Conflicts are visible while they can still be resolved – not during delivery crunch at 11pm. Cross-workload conflict detection becomes part of planning, not a late discovery.
Spot risks before they become incidents.
The dashboard surfaces cross-workload conflicts, availability heatmaps, and forecast data in one view. Risks that used to surface during a retro now appear at planning — before the deadline is already at risk.
Less reactive firefighting.
Delivery risk drops because capacity is a planning input, not a post-mortem finding. Managers stop absorbing pressure the data could absorb instead. The team ships on time more often because the plan matches what the team can actually do.
The specifics, for people who want them.
Plan sprints against real availability.
- Daily hour budgets per team member
- Rolling availability from approved leave and holiday schemes
- Gantt drag to shift task dates; resize to change duration
- Workload matrix by team and user
- Allocation drilldown for per-user detail
Red, amber, green at a glance.
- Overload indicators surface the moment they occur
- Filter by team, workload, user, or status
- Daily, weekly, monthly granularity
- Today-line marker for current position
- Gantt drag-and-drop to adjust task timing and duration
One view for the whole picture.
- KPI summary: capacity, planned work, and overload at a glance
- Capacity and planned work trend charts
- User availability heatmap for forward-looking planning
- Cross-workload conflict detection
- Forecast data and allocation drilldown
What Workload changes for each role.
CTO / IT Director
Cross-workload capacity visibility at a glance. Delivery risk becomes measurable, not anecdotal.
Project Manager
Sprint plans that match reality, not optimism. Assignment decisions take seconds with real capacity data.
Engineering Lead
Committed hours vs. availability visible before the sprint starts. Drag tasks on the Gantt to shift dates or resize duration — load numbers update immediately across the team view.
Delivery Head
Cross-workload conflicts visible at planning – before they turn into delivery crises. One consolidated view across all workloads.
Workload gets better with these.
Three ways to get Workload.
Workload – self-hosted
- 1 year of support included
- Renew support at 30% per year
- No licence keys · unlimited users · full source
Pick the plugins you need
Add Workload and the plugins it works with on the pricing page – see your one-time total, renewal and 3-year cost.
Build the stack →Redmineflux Cloud
- Workload and every other plugin included
- Fixed price per team size – never per user
- Hosted, backed up and updated by us
Questions teams ask before adopting Workload.
If yours isn’t here, check the pricing page or write to support@redmineflux.com.
How is this different from Redmine’s core assignment view?+
Core Redmine shows who’s assigned to what. Workload shows who has capacity for what – hours against availability, not just a count of tickets. Core Redmine doesn’t model working hours, PTO, or overload. Workload does, and updates in real time when assignments change.
Will it work with my Redmine version?+
Yes — the plugin supports all Redmine versions. Compatibility is verified with each plugin update.
How do working hours and PTO get into the plugin?+
Availability is derived from configured working hours per day, weekend settings, holiday schemes, and approved leave. A person on approved leave has 0 capacity for that day. Holiday schemes can be configured per region or per team.
How does Workload detect cross-workload conflicts?+
The dashboard surfaces cross-workload conflicts automatically — when a team member is over capacity across multiple workloads, the conflict appears in the dashboard before it becomes a delivery problem. Filter by team, workload, user, or status to drill into specific situations.
What happens to my data if I uninstall the plugin?+
Nothing. Workload derives its view from standard Redmine assignment data – it doesn’t introduce a separate data model. Uninstall the plugin and your Redmine issues, users, projects, and HR data remain untouched. No lock-in.
How much does the Workload Plugin cost?+
Workload is $499 one-time for self-hosted Redmine – 1 year of support included, then support renews at 30% of the plugin price per year. Or get every plugin hosted on Redmineflux Cloud from $69/month for up to 25 users – a fixed price, never per user.
Is there a free demo available?+
Yes – request a free demo and we’ll send a personalised demo link straight to your inbox. No credit card required, no commitment. Explore the real product at full capacity, at your own pace.
Every Redmineflux plugin
Workload running inside your Redmine.
$499 one-time on self-hosted Redmine – or every plugin on Cloud from $69/month.