Redmine Checklist – structured steps inside every issue.
For QA leads and engineering leads who need enforced completion criteria in Redmine.
one-time purchase · 1 year of support included
Support renewal after 1 year 30% of plugin price · install in 10 minutes
Today in Redmine
Partial delivery marked done is a delivery risk no one sees coming.
Without a structured definition of done inside each issue, work marked done under deadline pressure leaves QA steps unverified and deployment steps unenforced. There is no structural visibility into which sub-steps are complete and which are still outstanding. Inconsistent “done” criteria across team members makes sprint reviews longer and release confidence lower.
In plain words
What is the Redmineflux Checklist Plugin?
The Redmineflux Checklist Plugin adds configurable checklists directly inside Redmine issues. Each checklist contains discrete steps that must be checked off before the issue can be closed. Teams can define reusable checklist templates, track progress with visual indicators, and enforce issue closing until all steps are complete.
Every step visible. Every closure enforced.
The Checklist Plugin works as a structured completion layer at the issue level. Every step is explicit. Every closure is verified. Teams that previously relied on informal review processes to catch incomplete work replace that overhead with structural enforcement that operates automatically at the issue level.
Redmine, upgraded for delivery discipline.
What your team gains
Completion you can see, not assume.
Click any shift to see what changes in the product.
01
Issues cannot close until all required steps are complete.
Structural enforcement means completion standards apply consistently without project managers manually reviewing every issue before status changes are permitted. The tool enforces the rule automatically.
02
QA steps enforced structurally, not by convention.
Review and testing steps defined as mandatory checklist items cannot be skipped. QA leads who previously discovered that testing steps were bypassed after closure now have a structural mechanism that prevents closure before testing is confirmed.
03
One completion standard, applied across every team member.
Every engineer, QA analyst, and project contributor works to the same completion standard. Convention-dependent processes – where some team members follow the standard and others do not – are replaced by structural enforcement that applies uniformly.
04
Outstanding steps visible to the whole team in real time.
Completion progress is visible on the issue page without reading through comments or status history. Managers can see checklist completion status directly on the issue page without reading through comments or status history.
05
Review cycles faster through visible completion state.
Reviewers and QA leads can assess issue readiness from the list view before opening individual issues. This reduces the time spent in review on issues that are not yet ready for inspection.
Core capabilities
The specifics, for people who want them.
Add discrete, trackable steps to any Redmine issue.
- Multiple checklists per issue, each with its own list of items
- Item statuses: New, In Progress, and Done for granular step tracking
- Title and description text fields for each checklist item
- Progress indicator shows how many steps remain at a glance
Prevent partial closure with structural controls.
- Global setting blocks issue closing until all checklist items are ticked
- Configured once in Admin > Plugins > Checklist > General tab
- Visual progress indicator on the issue page
- Checklist items remain visible on the issue for full team transparency
Build standard checklists once, apply them consistently.
- Save checklist templates and apply with a single action
- Templates configured at admin level and linked to a specific tracker
- Apply a template to any issue with a single action
- Managed in Admin > Plugins > Checklist > Templates tab
See completion state at a glance inside every issue.
- Items support New, In Progress, and Done statuses
- Visual progress bar shows how many steps are complete at a glance
- Simple checkbox mode also available per item
- Multiple checklists per issue for distinct task groups
Control who can create, edit, and complete checklist items.
- Role-based permissions for creation vs. completion
- Read-only access for stakeholders and observers
- Per-project permission configuration
- Permissions follow your existing Redmine role configuration
200+
teams trust Redmineflux worldwide
6 yrs
focused on Redmine, nothing else
5000+
plugin downloads powering real projects
Deployment steps used to be a convention that some engineers followed and others skipped. Since we embedded them as mandatory checklist items, every deployment follows the same process – no exceptions.
Deployment
Run it your way.
Managed Cloud
- Hosted by Redmineflux · included in every Cloud plan
- Daily backups · SLA-backed uptime
- No per-plugin licences – all-inclusive pricing
$1.99 / user / month
Get a Free Demo →Self-hosted
- One-time purchase · 1 year of support included
- Your infrastructure, your security perimeter
- Install in 10 minutes
From $49 one-time
Buy plugin →Every plugin in Cloud also runs on self-hosted Redmine.
Role by role
What Checklist changes for each role.
Project ManagerDelivery governance, closure standards
Consistent closure criteria across all tasks, projects, and delivery cycles – without manually reviewing every issue before a status change is permitted.
QA LeadTesting enforcement, review readiness
QA and testing steps enforced structurally before any issue reaches closed status – eliminating the post-closure discovery of bypassed testing steps.
Engineering LeadReview, deployment, code quality
Structured review, code check, and deployment checklists embedded in every issue – so the process is the same regardless of who is closing the ticket.
IT DirectorCompliance, audit, governance
Governance over delivery standards with consistent closure enforcement – no step bypassed, no partial delivery marked done across any issue in any project.
Pricing
Three ways to get Checklist.
Buy this plugin
Checklist – self-hosted
Support renewal after 1 year 30% of plugin price
1 year of support included · install in 10 minutes
Buy Checklist →Save with a Bundle
All Plugins Bundle
Every plugin + Daisy and Scarlet themes.
Save 10% See the Bundle →Or use Managed Cloud
Redmineflux Cloud
Included in every Cloud plan from $1.99/user/month. Managed Redmine, no infrastructure work.
See Cloud plans →See enforcement in your issues
See Checklist running in your Redmine.
Real checklists, real enforcement, real mandatory steps – running inside Redmine.
Frequently asked
Questions before you install.
The questions teams actually ask before adopting Checklist. If yours isn't here, check pricing or contact support.
Can checklist items be required before an issue can be closed?
Yes. When the Block issue closing option is enabled, an issue cannot be set to a closed status until all checklist items are ticked. This is a global setting configured in Admin > Plugins > Checklist > General tab. It applies across the installation and does not require per-tracker or per-project setup.
Can I reuse checklists across multiple issues?
Yes. Checklist templates can be configured and applied to new issues. Templates are created in Admin > Plugins > Checklist and linked to a tracker, giving teams a consistent starting checklist for each issue type.
What progress statuses do checklist items support?
Checklist items can be set to New, In Progress, or Done. A visual progress bar on the issue shows how many items are complete at a glance. Items can also be tracked with a simple checkbox. Multiple checklists are supported per issue for distinct task groups.
Which Redmine versions are supported?
The Redmineflux Checklist Plugin supports all Redmine versions. Compatibility is verified with each plugin update.
How much does the Checklist Plugin cost?
$49 one-time for self-hosted – 1 year of support included. Support renewal after 1 year 30% of plugin price. Bundle with the All Plugins Bundle ($4,754 one-time) for all plugins. Or hosted at $1.99/user/month via Redmineflux Cloud – included in every plan. See the pricing section above.
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. Cloud starts at $1.99/user/month.