Checklists & close guards

Issue checklists

When the project module is enabled, permitted users can view, add, edit, complete, reopen, and delete flat checklist items. Checklist changes are stored separately and do not create issue journals or notification mail.

Enable access

1. Keep the checklist feature enabled under Configure → Issues.
2. Enable the Redmine UX Toolkit module in the project.
3. Grant View checklists to readers and Edit checklists only to roles that may change items.
4. Open an issue as the target role and confirm that the checklist section and edit controls match the granted permissions.

Edit an issue checklist

1. Open the issue and expand the checklist controls.
2. Add a short checklist item, or preview an active template and insert it.
3. Mark items complete as work finishes. Completed items can be reopened; permitted editors can rename or delete items.
4. Review the progress count before closing the issue. Checklist changes are saved separately and do not produce issue journals or notification email.

Templates and tracker defaults

Administrators maintain active global templates with ordered items. Editors can preview and append a template manually, or a tracker default can copy items once when an issue is created.

• Manual insertion appends new open items after the issue's existing checklist.
• Tracker defaults run only when a new issue is created, not when an existing issue later changes tracker.
• Inserted items are independent copies; editing or disabling the source template does not alter existing issues.

Close guards

Optional validation blocks closure while checklist items or direct subtasks remain open. It applies to normal edits and plugin quick actions without changing child issues.

Resolve a blocked closure

1. Read the validation count to determine whether open checklist items or direct subtasks caused the block.
2. Complete the remaining checklist items or close the relevant direct subtasks using their normal workflows.
3. Save the parent issue with a closed status again. The guard checks only the open-to-closed transition and never closes child issues automatically.