Redmine Products / Templates Plugin for Redmine - Templates for issues and notes

Coming soon: The Templates Plugin is currently in the final stages of preparation for release. Once released, it will be available as an individual license or as part of the Enterprise+ Bundle.

Templates for issues and notes - define once, reuse anywhere.

Templates Plugin - templates for issues and journal notes

Reusable templates for issues and notes

The Templates Plugin brings a consistent template system to Redmine. Anyone who repeatedly creates similar issues or writes the same kind of replies stores the pattern once as a template and pulls it back into the form with a single click.

Anyone who repeatedly creates similar issues or writes the same kind of replies in Redmine knows the problem: copy & paste from older issues, varying wording, forgotten fields. The Templates Plugin captures the pattern cleanly as a template once - delivering consistent issues and uniform language in replies.

Who the Templates Plugin is for:

  • Support and helpdesk teams that answer recurring requests with standard replies.
  • Project managers who model structured requests, onboardings or releases as issue templates.
  • Teams with multi-project structures that want to enforce company-wide standards with inheritance to sub-projects.

Your benefits at a glance

Two template types under one roof

Issue templates pre-fill key fields like subject, description, tracker etc. Reply templates provide reusable text for journal notes.

Global or project-specific

Templates can be used globally or scoped to a single project - depending on how you want to manage your standards.

Inheritance to sub-projects

Templates can be passed down to all sub-projects when needed. You stay in control of every step of the inheritance chain.

Default template per tracker

Set a default template per tracker. It is automatically pre-selected when a matching issue is created and ensures immediately consistent issues.

Visibility via groups

Use public or private templates, or assign them to specific user groups - visibility is easy to control.

Tag support for large libraries

Templates can be tagged, which keeps them easy to find even in extensive template libraries.

FAQ
+
The Templates Plugin is a commercial extension by AlphaNodes that brings a consistent template system to Redmine. Reusable templates for issues and journal notes are stored once and recalled into the form with a single click - usable globally or project-specific.
+
The plugin supports two types: issue templates pre-fill key fields of a new issue (subject, description, tracker, status, priority, assignee, watchers, date offsets, custom fields). Reply templates provide reusable text for journal notes - ideal for recurring status updates or standard follow-up questions.
+
Templates from a parent project can be passed down to all sub-projects when needed. Inheritance is activated per sub-project and released per template - so you keep control over which templates apply where, while still maintaining cross-project standards centrally.
+
Yes. A default template can be defined per tracker. It is automatically pre-selected when a new issue with this tracker is created. New issues are consistent from the start, without users having to look for the right template themselves.
+
Templates can be kept private (visible only to the creator), assigned to specific user groups, or released publicly for all authorized users. This allows granular control for sensitive or role-based workflows.
+
The Templates Plugin is an in-house development by AlphaNodes built on our plugin suite. From the start it covers both issue templates and reply templates for journal notes. Unlike pure issue-template solutions, the plugin is architecturally designed to support additional Redmine entities going forward.
+
Yes, the plugin integrates seamlessly into existing Redmine instances and uses the established permission logic of Redmine and the AlphaNodes plugin suite. Optionally, the plugin also handles checklist entries from our redmine_issue_checklists and uses additional_tags to classify large template libraries.
+
Your Redmine installation must meet our current minimum requirements. These can change with new plugin versions. Check the current requirements before purchase.