We already use another resource planning plugin. Can we switch?

Yes, and we will help you migrate. Contact us with the name of the plugin you use today, and we will help you move your existing data into Resource Planner.

Do I have to re-enter my people and projects?

No. The planner uses the users, groups, projects and issues already in your Redmine. A booking on an issue links back to that issue, and spent time is read from Redmine’s own time entries.

How is capacity calculated?

Each working day counts for the daily capacity you set, eight hours by default. Weekend days, holidays assigned to the person and approved leave count as zero. Bookings are measured against that, which gives utilisation, remaining hours and overbooked days.

Can team members see each other’s bookings?

That depends on the permissions you grant. Someone with only their own planner sees the “Me” calendar. Managers who are not administrators see the people who share one of their projects. Administrators see everyone.

What happens when I book someone who is already busy?

With conflict validation on, the plugin warns about the overlap and blocks the save. A manager can choose to override it. If overlaps are normal for your team, you can allow them in the settings.

Can I add booking types of my own?

Yes. Add types such as support, on-call or travel in the plugin settings, each with a label and colours. They appear in the booking form, the legend and the filters.

Are the screenshots real?

They are real screens from the plugin on Redmine 6.1, taken from a demo team we created for this page. The people, projects and numbers are made up. They show what you will see for your own team, not results from a customer.

Redmine Resource Planner

Planning

5.0 (0)·New installs

See who is working on what, and who has room for more. Book people onto issues, meetings, training and leave on a drag-and-drop board, with capacity, overbooking and the weeks ahead worked out from your working hours, holidays and approved leave.

$199 / single server

Multiple servers: $399

5-working-day refund12 months updatesSource included

The Resource Planner board in Redmine, week view for a team. Each person has a row and each day a column. Green issue bookings, orange sprint planning meetings, pink support windows and a red sick-leave block fill the grid. Each day shows the hours booked, with 11h flagged in red on two days for one person, and a weekly total sits next to every name. — Week view One row per person and one column per day, with the hours booked each day and overbooked days flagged in red.

Redmine: 4, 5, 6 and 7
Views: Day, week, month, range
Booking types: 4 built in, plus your own
Dashboard widgets: 11
Databases: MySQL, MariaDB, PostgreSQL
API: JSON, API-key auth

Drag, drop and resize

Move a booking to another day or another person, or drag its edge to make it longer. Day, week, month and date-range views, filtered by project, person, group or booking type.

Conflict detection

The plugin warns when a booking overlaps another one for the same person. Managers can override when it is intended, or you can allow overlaps altogether.

Recurring bookings

Daily, weekly or monthly, on the weekdays you pick, until a date or for a number of occurrences, skipping weekends and holidays if you want.

Capacity and forecast

Available, planned and remaining hours for every person, with utilisation for the next 30, 60, 90 and 180 days and the days you will be short.

Leave the plan knows about

Anyone can request leave. Once a manager approves it, it appears on the board and the person’s capacity drops for those days.

Your users, projects and issues

Bookings sit on top of the Redmine data you already have. Issue bookings link back to the issue, and spent time comes from Redmine’s own time entries.

Holidays built in

Add public holidays by hand or import them from CSV or Excel, per country, one-off or repeating every year. Assign them to groups or to individual people, and those days count as zero capacity.

From a booking to a forecast, with nothing entered twice

Bookings sit on top of the users, projects and issues you already have in Redmine. Everything else on this page is calculated from them.

1. Working time

Daily capacity, weekend days and public holidays, assigned per person or per group.

2. Bookings

Issues, meetings, training and your own types, placed on the board by drag and drop.

3. Leave

Requested by the employee and approved by a manager. Approved leave becomes a booking and removes capacity.

4. Capacity

Available, planned and remaining hours, utilisation and overbooked days for every person.

5. Forecast

Utilisation for the next 30, 60, 90 and 180 days, and the days you will be short.

One source of truth

Each step reads the one before it. Spent time comes from Redmine’s own time entries, issue bookings link back to the issue, and there is a global board, a project board and a personal “Me” calendar.

Already using another resource plugin?

We will help you migrate. Tell us which plugin you use today, and we will help you move your existing plan into Resource Planner, so your team does not have to start from an empty board.

The board your team will actually open every morning

These are real screens from the plugin on Redmine 6.1, with a demo team of eight people across three projects.

Plan: a month of work for the whole team

Switch between day, week, month or any date range. Filter by project, person, group, booking type, or search by title.

The planner board in month view, filtered to the Product Team group. Rows for Ben Carter, Farid Haddad, Aisha Khan, Grace Liu and Chloe Martin show bookings across October: issue work in green, meetings in orange, a training workshop in purple, support windows in pink and sick leave in red. Hours booked per day appear above each cell, with overbooked days in red, and a monthly total next to each name. — Month view Colour shows the kind of work, the small badge shows hours booked that day, and red badges mark the days someone has more than their capacity. Weekends are shaded as non-working.

The new planner item dialog over the board: item type, title, user, project, issue search, start and due date and time, description, and a repeat section set to weekly with an interval, number of occurrences, weekday checkboxes, an end date and options to skip weekends and holidays. — New booking Pick a type, a person and an issue, set the times, and repeat it daily, weekly or monthly. Recurring bookings can skip weekends and holidays.

The week board grouped by project. Under each person, collapsible project groups such as Customer Support and Website Relaunch list each booked issue on its own line across the week. — Grouped by project The same week as a tree: person, then project, then one line per issue. Collapse the projects you do not need.

Check: who is free, and what was actually worked

Two more ways to look at the same week, one click away on the toolbar.

The availability view for the week: one row per person and one cell per day, coloured and labelled Full 8h, 7h free, 8h free, Overbooked 11h, On leave or Non-working, with a legend for free, light, busy, full and overbooked. — Availability One cell per person per day: how many hours are free, who is full, who is overbooked and who is on leave. This is the view to open when new work arrives.

The spent time view for the week: for each person, planned hours against hours logged per day, with a summary of spent, planned and estimated hours and a progress bar under each name. — Planned against spent Hours booked on each day next to the time people logged in Redmine, with spent, planned and estimated totals per person.

Balance: capacity planning and forecast

Capacity is working days times daily hours, minus holidays and approved leave. Bookings are counted against it.

The capacity planning page for October: 1,352 hours available, 1,189 planned, 163 remaining, 88% utilisation, 26 hours overtime and 189 idle. Below, a table lists eight people with available, planned and remaining hours, a coloured utilisation bar and the number of shortage days. — Capacity planning Available, planned and remaining hours for the team and for each person, with utilisation bars and a count of the days each person is short.

The forecast page: utilisation of 65% over the next 30 days, 32% over 60, 21% over 90 and 10% over 180, and a table of eight people with their utilisation for October, November and December, two of them flagged as overallocated. — Forecast How booked the team is over the next 30, 60, 90 and 180 days, month by month for each person, with overallocation flagged early.

A manager dashboard with nine widgets: team capacity, resource utilisation per person from 110% down to 45%, overbooked resources, upcoming leave, resource forecast, a workload trend bar chart, project allocation in hours for three projects, a utilisation heatmap by person and day, and a list of expiring allocations. — Dashboards Build personal, shared or per-project dashboards from eleven widgets: team capacity, utilisation, overbooked people, upcoming leave, forecast, workload trend, project allocation, a utilisation heatmap and more.

Leave: time off that the plan knows about

Anyone can request leave. Once a manager approves it, it appears on the board and the person’s capacity drops for those days.

The leave approvals page with three pending requests showing the person, leave type of vacation or personal, start and due date, number of days and reason, each with a comments field and Approve and Reject buttons. — Approvals Pending requests with dates, days and reason. Approve or reject with a comment, and the employee is notified by email.

The request leave form with a leave type, start date, due date, a reason field and a Submit request button. — Request leave Vacation, sick, personal, unpaid or other, with dates and a reason.

Administer: reports, holidays and settings

The resource planner report in Administration: filters for project, user, planner type, dates and grouping, totals of 263 assignments, 520 estimated hours, 1,357 planned hours and 272.5 spent hours, and a table per person with assignments, estimated, planned, spent and remaining hours. — Report Estimated, planned, spent and remaining hours, grouped by person, project or booking type.

The holidays page: import holidays from CSV or Excel with a downloadable sample, a form to add holidays with a country, name, date and a recurring option, and the list of holidays for the year. — Holidays Add them by hand or import from CSV or Excel, per country, one-off or yearly. Assign them to groups or to individual people.

The plugin settings: conflict validation, allow overlapping bookings, daily capacity hours, default planner view, default landing view, default start and end time, non-working weekend days, and the issue statuses shown in the planner. — Settings Daily capacity, working hours, weekend days, conflict rules, default view, booking types and their colours.

Planning that stays in step with the issue tracker

Drag, drop and resize

Move a booking to another day or another person, or drag its edge to make it longer. Select several and shift them together.

Conflict detection

The plugin warns when a booking overlaps another one for the same person. Managers can override when it is intended, or you can allow overlaps altogether.

Recurring bookings

Daily, weekly or monthly, on the weekdays you pick, until a date or for a number of occurrences, skipping weekends and holidays if you want.

Your own booking types

Issue, meeting, leave and training come built in. Add your own types, such as support or on-call, each with its own colour.

Workload balancing

When someone is overbooked, the balancing page suggests moving a booking to a colleague with free hours, or to a later date. Nothing changes until you apply it.

Global, project and personal

One board for everyone, one inside each project, and a “Me” calendar for each person’s own bookings. What you see follows your Redmine permissions.

Bookings, capacity and forecast as JSON

Every endpoint authenticates with a normal Redmine API key and follows the same permissions as the screens. Project-scoped variants exist under /api/projects/:id/…

Paths are relative to /api/resource_planner
Method	Endpoint	Purpose
GET	/bookings	Bookings, workload and spent time for a range
POST	/bookings	Create one or many bookings
PATCH	/bookings/:id	Move, resize or edit a booking
DELETE	/bookings/:id	Remove a booking
GET	/issues	Assigned issues that can be booked
GET	/capacity	Available, planned and remaining hours
GET	/forecast	Future utilisation and shortages
GET	/holidays	Holiday list, with create, update and delete
GET	/report	The utilisation report

Book three people into one meeting

Pass several user ids to POST /bookings to create the same booking for each of them. It is all or nothing: if one fails, none are created. A clash with an existing booking returns 409, and validation errors return 422.

Seven permissions, granted per role

Resource Planner is a standard Redmine project module. Administrators see everyone. Other managers see and manage only the people who share a project with them.

Permission	What it allows
view_resource_planner	Open the board, read only
manage_own_resource_planner	Create and change your own bookings in the “Me” planner
manage_others_resource_planner	Create and change bookings for other people
view_capacity_planning	See capacity, utilisation, balancing and dashboards
view_forecasts	See the forecast
approve_leave_requests	Approve or reject other people’s leave. Requesting your own leave needs no permission.
manage_dashboards	Create shared and project dashboards and arrange their widgets

Runs where your Redmine already runs

Environment	Status	Notes
Redmine 7.x	Supported
Redmine 6.x	Supported	Tested on Redmine 6.1 with Ruby 3.4.2. The screenshots on this page are from 6.1.
Redmine 5.x	Supported
Redmine 4.x	Supported	4.0 is the minimum version the plugin declares
Databases	Supported	MySQL, MariaDB and PostgreSQL
Languages	51	The same locales Redmine ships with
Your data	Unchanged	Uses Redmine’s users, groups, projects, issues and time entries as they are

Install in three steps

Requires shell access and the ability to run rake tasks. Always back up before installing a plugin.

Unpack into your plugins folder

cd /path/to/redmine
# the package arrives by email, or from your download link
# the folder must be named plugins/resource_planner
unzip resource_planner-0.1.0.zip -d plugins/

Migrate and restart

RAILS_ENV=production bundle exec rake redmine:plugins:migrate NAME=resource_planner
touch tmp/restart.txt   # or systemctl restart redmine

Turn it on in Redmine

# Administration → Roles and permissions → grant the Resource Planner permissions
# Project → Settings → Modules → tick Resource Planner where you want a project board
# Administration → Plugins → Resource Planner → daily capacity, working hours, weekend days
# Administration → Resource Planner → Holidays → add or import your public holidays