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 project's Auto Assign, Checklists, Agile and Banner
settings. New projects start from the gallery instead of from an empty form.
A template is a stored definition, not a live project. Everything in it is
recorded by name, so it keeps working after the project it came from is
renamed, archived or deleted. It also carries less than Redmine's Copy does.
See What a template does not carry below.
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 kept, skipped when a project is created, and kept again by Re-snapshot, and the rest still works.
Mail is held back only for the request that is building a project, never switched off for the whole server, so everyone else's notifications go out as usual while a project is being built.
A template holds up to 15 MB, on every supported database.
Update and remove
Copy the new directory over the old one, run the migrate command, restart. The migration makes template names unique regardless of case on PostgreSQL, as they already are on MySQL and MariaDB; where names differ only in case, every template after the oldest gets its database id added in brackets, such as Onboarding (17).
Version 2.0.0 is a major version because a template now adds no authority (see above): someone whose role in new projects cannot manage members used to get every member a template named, and no longer does.
Version 1.1.x cannot use a template written by 2.0.0, and every template saved
as a template, re-snapshotted or created blank on 2.0.0 is one. 1.1.x still
lists it in the gallery and opens its form, then refuses it on Create, saying
the template was written by a newer version of the plugin and cannot be used.
It works again once 2.0.0 is back. The other way round works: templates
written by 1.1.x keep working on 2.0.0 without losing anything they hold, and
editing one there keeps it readable by 1.1.x.
On MySQL or MariaDB, delete the templates from the template list before you remove the feature, at least every one larger than 64 KB; removing it deletes them anyway. Otherwise the removal stops part-way: MySQL refuses to shrink the column that holds a template back to 64 KB while one is larger, two other columns have been dropped by then, and running the command again fails too.
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.