How each of RedminePRO's built-in features works and how to configure it in your own workspace: settings, permissions and per-project options. On RedminePRO Cloud, installing, updating and maintaining the features is our job. Every feature can also be installed on your own Redmine, and each one has a page for that.
Sectioned checklists on every issue, with templates, per-item assignees and due dates, and optional workflow enforcement.
One email a day per person covering their overdue, due and newly assigned work, sent at an hour they choose.
A personal dashboard of your open work, workload and logged time, with widgets you arrange yourself.
Click an attachment and it opens in a popup, images, PDFs and text, without the download-to-look cycle.
Click a field on an issue and edit it in place, with the same permissions, workflow rules and history as the full form.
Let someone approve registrations, create people and lock leavers without making them a full administrator.
Adds a role visibility option where past involvement counts, so people keep access to issues they worked on.
Ask questions of your workspace and draft issues with AI, using your own provider account and your own permissions.
A Kanban or Scrum board over your issues, with sprints, work-in-progress limits, story points and flow charts.
An append-only record of deletions, administration changes, security events and bulk edits, with alerts and retention.
Let people sign in with their Google account, with optional domain restriction and a password-free workspace.
A per-ticket start and stop timer that logs into Redmine's own spent time, plus a timesheet over the same data.
Assign an issue automatically when it reaches a status, with rules per project or shared rule sets.
Show a scheduled notice across the workspace or on one project, styled by severity and optionally dismissible.
An editable Gantt chart that replaces the built-in one, with dependencies, critical path, baselines and a cross-project view.
Link commits and track pull requests on your issues, driven by webhooks from a GitHub App you own.
Turn support email into tickets, track response times against a service level, and give customers a portal for their own tickets.
Turn your workspace into an MCP server so Claude or any Model Context Protocol client can work on issues as a real person.
Let people sign in with their Microsoft work account from your directory, with optional domain restriction.
Start a project from a template that brings its structure, starter issues, members and feature configuration with it.
Save a report built from Redmine's own filters and columns, re-run it any time, and export or email it as PDF, Excel or CSV.
See who is over-committed before the sprint starts, from assigned work, estimates and recorded leave.
Lifecycle, effort, workload and health charts over your issues, per project or across all of them.
Edit Redmine status transitions as a flow chart instead of a checkbox grid, over exactly the same rules.
The hosted essentials, your plan and how many seats it allows, plus the support link in the top menu.
A feature's settings for the whole workspace are under Administration → Plugins, on that feature's own page. Each configuration guide names the page and what every setting on it does.
Who may use a feature is set under Administration → Roles and permissions, in that feature's section of the role form. The guides list each permission and what it grants.
Most features are switched on per project, under the project's Settings → Modules. A feature that is a module appears only in the projects where it is ticked.
Every plan includes full Redmine admin access, so all of the above is yours to set. Installing, updating and maintaining the features themselves is ours.
The same guides as two lists: every configuration guide and every installation guide.
Longer pieces on running Redmine rather than configuring it are on the blog.