Redmine Products / Templates Plugin for Redmine for creating templates

Coming soon: The Templates Plugin will be released soon. It will then be available as an individual license.

Templates for adding new projects, issues, issue comments and wiki pages - define once, reuse anywhere.

Templates Plugin - templates for new issues, wiki pages, issue comments, projects

Reusable templates for adding new projects, issues, issue comments and wiki pages

Reusable templates for adding new projects, issues, issue comments (canned responses - ServiceDesk Plugin) and wiki pages. The template is selected when creating new content - not applied to existing items. Defined once, reused with a single click - globally or project-specific, with inheritance to sub-projects and group-level visibility.

Whether standardized project onboardings, recurring issue types like release or test issues, or consistent wiki pages for meeting notes: with the Templates Plugin you define the structure once as a template and apply it with a single click when adding new content. This speeds up recurring workflows and ensures consistent results across the entire team.

Who the Templates Plugin is for:

  • Teams that want to start recurring project types like onboardings, audits or implementations from project templates in a standardized way.
  • Project managers who model structured issues for defined activities (e.g. releases, tests, tasks) as issue templates.
  • Documentation and knowledge teams that maintain wiki pages with a consistent structure - e.g. meeting notes, release notes, how-to articles.
  • Teams with multi-project structures that want to enforce company-wide standards with inheritance to sub-projects.

Your benefits at a glance

Supports different template types

Issue templates pre-fill key fields like subject, description, tracker etc. when adding a new issue. Project templates help to start new projects with members, versions, issues and wiki quickly. Wiki templates provide defaults for new wiki pages (including title, content and tags).

Canned responses when using ServiceDesk

Respond quickly and consistently with prepared answers (canned responses). Available when using the ServiceDesk Plugin.

Global or project-specific

Templates can be used globally or scoped to a single project. Depending on how you want to manage these standards.

Inheritance to sub-projects

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

Versioning with comments

Every change to a template is recorded in the version history with author, timestamp and an optional comment. That way, who changed what and when is fully traceable at any time.

Visibility via groups

Use public or private templates, or assign them to specific user groups. Visibility is easier to control this way. Group members only see what they really need.

Tag support for template categorization

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

File attachments on templates

Issue and wiki templates can carry file attachments. When applied, an independent copy lands on the new issue or new wiki page.

Save a running project as a template

From any existing project a so-called blueprint can be created via the “Save as project template” action. Without affecting the running project. This lets you create a template based on the current state of the project.

Even more possibilities when combined with other AlphaNodes plugins

  • ServiceDesk Plugin: Reply templates (canned responses) for recurring standard replies to helpdesk issues - including helpdesk- and contact-specific variables.
  • Automation Plugin: Dynamic placeholders in template texts - e.g. for project name, current user or date. Replaced server-side with the actual values when applied.
  • Issue Checklists Plugin: Issue templates can carry checklists that appear directly on the new issue when applied.
  • Reporting Plugin, DB Plugin, Passwords Plugin and more: When cloning a project template, the contents of these additional plugins from our product portfolio are automatically carried over.
FAQ
+
The Templates Plugin is a commercial extension by AlphaNodes that brings a consistent template system to Redmine. Reusable templates for issues, projects and journal notes are stored once and recalled with a single click - usable globally or project-specific.
+
The plugin supports three 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 issue comments - ideal for recurring status updates or standard follow-up questions. Project templates help to start new projects with the same structure quickly.
+
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. Every change to a template is recorded in the version history - with author, timestamp and an optional comment for the change. The version list is visible on the template's detail page, so it is always traceable who adjusted what and when on a template.
+
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 issue templates, reply templates for issue comments, and project templates. 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. In a helpdesk context, only our own ServiceDesk Plugin is supported - other helpdesk products are not covered.
+
Your Redmine installation must meet our current minimum requirements. These can change with new plugin versions. Check the current requirements before purchase.