Every new client onboarding, every new release, every new audit — the same
shape, rebuilt by hand each time. A template captures that shape once: the
Structure, the Starter issues with dates relative to a start day you choose,
the Members, and the configuration of other features that project used. New
projects start from the gallery instead of from an empty form.
A template is a stored definition, not a live project. That is the whole difference from copying: it keeps working after the project it came from is renamed, archived or deleted, because everything in it is recorded by name.
On your own Redmine
Requirements
- Redmine 6.0 or newer (Rails 7.2, Ruby 3.1 or newer)
- PostgreSQL 14+, or MySQL 8.0+ / MariaDB 10.6+
- No additional gems
Install
cd /path/to/redmine
cp -r redminepro_project_templates plugins/
RAILS_ENV=production bundle exec rake redmine:plugins:migrate NAME=redminepro_project_templates
# restart Redmine
Standalone behaviour
Identical. No plan gate applies, and the Project Templates module hides its own
checkbox from project settings — templates are a workspace-level idea, not a
per-project one.
The configuration it carries for other features is stored as an opaque record, so a template made while another feature was installed stays valid if that feature is later removed: the unknown part is skipped and the rest still works.
Update and remove
Copy the new directory over the old one, run the migrate command, restart. To remove:
RAILS_ENV=production bundle exec rake redmine:plugins:migrate NAME=redminepro_project_templates VERSION=0
rm -rf plugins/redminepro_project_templates
# restart Redmine
Templates go. Every project ever created from one stays exactly as it is — they were ordinary projects the moment they were made.
Already on RedminePRO Cloud? It is installed and maintained for you: see the configuration guide.