Redmine Issue Template – standardize every task from the start.
For project managers and engineering leads who need consistent, complete issues every time.
Incomplete issues cost more time than the task itself.
When teams create issues without a standard format, required fields turn up missing mid-sprint and work stops while context gets filled in retrospectively. Developers spend time asking for clarification on poorly written or incomplete issues. QA teams lack acceptance criteria and cannot test reliably when the definition of done was never written into the original issue.
Standards enforced at creation, not corrected after.
The Issue Template Plugin works as a structured creation layer at the start of every task. Every template enforces the right format for its tracker type. Every issue created from a template carries the correct context from the first line.
Teams that previously relied on convention – or on project managers correcting incomplete issues before sprint start – replace that overhead with a structural standard that applies automatically whenever a new issue is created.
What is the Redmineflux Issue Template Plugin?
The Redmineflux Issue Template Plugin adds reusable templates to Redmine’s issue creation flow. When a team member creates a new issue, they select the relevant template and the description structure and subject are pre-filled instantly. Every issue starts with the right context.
Every issue starts complete, not half-filled.
Pick a shift to see what changes in the product. They play on their own – hover to pause.
Every issue starts with the right context, always.
Tasks created from a template contain complete information and the correct structure for their tracker type. No missing fields, no absent acceptance criteria, and no vague descriptions to correct before work can begin.
No more back-and-forth between creator and assignee.
Missing context does not surface mid-sprint when it was never missing in the first place. Developers receive issues that contain everything they need to begin work without requesting clarification from the original reporter.
Sprint planning without the issue-repair round.
Well-formed issues require no repair before sprint assignment. Project managers spend less time correcting templates during planning and more time assessing priority and sequencing the work that actually delivers value.
QA readiness from the moment of creation.
Acceptance criteria are present from the moment of creation rather than added as an afterthought. QA teams can plan testing cycles before sprint work begins rather than waiting for requirements to be retrofitted into existing issues.
New team members follow the right format from day one.
New engineers and project staff follow the right format from day one without needing training on what each tracker type requires. The template enforces the standard structurally – no manual oversight required.
The specifics, for people who want them.
Build structured templates for any issue type your team uses.
- Rich text template body for any tracker – Bug, Feature, Task, Support, custom
- Tracker and project scope configured per template for context-specific availability
- Templates scoped to specific projects or made globally available across all projects
- Default template auto-loaded by tracker type when a new issue is created
Apply the right template to the right context, automatically.
- Templates assigned to specific trackers within specific projects
- Multiple templates per tracker for different use cases
- Global templates available across all projects
- Default template auto-selected by tracker type when creating a new issue
Subject and description pre-filled the moment a new issue opens.
- Subject and description pre-filled from the template at issue creation
- Default template auto-loaded by the selected tracker type
- Switch templates at creation time if multiple templates exist for that tracker
- Global templates available alongside project-specific ones in every project
Manage your full set of templates from one admin interface.
- Centralised interface for creating, editing, and deleting templates
- Global templates managed in Administration > Issue Template
- Project templates visible alongside global templates within each project
- Project filter with auto-scroll for fast project assignment when editing templates
Control who can create and modify templates.
- Role-based permissions for template creation vs. application
- Users can apply templates without editing them
- Project-level admin control per template scope
- Project members can apply templates without permission to edit them
What Issue Template changes for each role.
Project Manager
Consistent issue quality and faster triage across all projects and trackers – without a manual review round before every sprint.
Engineering Lead
Clear, complete tasks from creation – no time lost correcting missing context or chasing reporters for additional information mid-sprint.
QA Lead
Acceptance criteria present in every issue before it reaches the QA stage – no waiting for requirements to be retrofitted into existing tickets.
IT Director
Standardised workflow governance and consistent data across the Redmine instance – enforced at the point of creation, not corrected after the fact.
Issue Template gets better with these.
Three ways to get Issue Template.
Issue Template – self-hosted
- 1 year of support included
- Renew support at 30% per year
- No licence keys · unlimited users · full source
Project Management bundle
Issue Template plus the plugins it works best with, at a published discount. Themes included.
See the bundle →Redmineflux Cloud
- Issue Template and every other plugin included
- Fixed price per team size – never per user
- Hosted, backed up and updated by us
Questions teams ask before adopting Issue Template.
If yours isn’t here, check the pricing page or write to support@redmineflux.com.
Can templates be assigned to specific projects or trackers?+
Yes. Templates in the Redmineflux Issue Template Plugin can be assigned to specific projects, specific trackers, or both. When a team member creates a new issue, the relevant templates for that tracker are shown. You can also configure a default template that loads automatically for the selected tracker.
Can I create multiple templates for the same tracker?+
Yes. You can create as many templates as needed for a single tracker. A Bug tracker can have separate templates for frontend bugs, backend bugs, and performance issues – each with a different subject prefix and description structure. The team member selects the most relevant template at creation time.
How does default template auto-selection work?+
When creating a new issue, the user selects a template based on the tracker type. Once selected, the subject and description are automatically pre-filled. Multiple templates can exist for the same tracker, and the user can switch between them at creation time.
Which Redmine versions are supported?+
The Redmineflux Issue Template Plugin supports all Redmine versions. Compatibility is verified with each plugin update.
How much does the Issue Template Plugin cost?+
Issue Template is $99 one-time for self-hosted Redmine – 1 year of support included, then support renews at 30% of the plugin price per year. It is also part of the Project Management bundle (save 7%). Or get every plugin hosted on Redmineflux Cloud from $69/month for up to 25 users – a fixed price, never per user.
Is there a free demo available?+
Yes – request a free demo and we’ll send a personalised demo link straight to your inbox. No credit card required, no commitment. Explore the real product at full capacity, at your own pace.
Every Redmineflux plugin
Issue Template running inside your Redmine.
$99 one-time on self-hosted Redmine – or every plugin on Cloud from $69/month.