Actions
Sprint Close – Saved Queries (Before Closing)¶
- Table of contents
- Sprint Close – Saved Queries (Before Closing)
Purpose¶
Saved queries act as validation gates during sprint close.
All blocker queries must be empty before proceeding.
Q1 – All Sprint Items (Working Set)¶
Purpose: Master list of sprint items
- Filters:
- Fixed version = Sprint 2025-03
- Columns:
- Tracker, Subject, Status, Assignee, Priority
- Story Points, Completed In Sprint, Spillover Reason
- Saved as:
Sprint Close – All items (Sprint 2025-03)
Q2 – Completed Candidates (Verification)¶
Purpose: Identify items marked Done but missing fields
- Filters:
- Fixed version = Sprint 2025-03
- Status = Done / In Review
- Saved as:
Sprint Close – Done in sprint version (verify fields)
Q3 – DONE but Missing Completed In Sprint (BLOCKER)¶
Purpose: Prevent history loss
- Filters:
- Fixed version = Sprint 2025-03
- Status = Done
- Completed In Sprint = empty
- Rule:
This query must be empty
- Saved as:
Sprint Close – Missing Completed In Sprint (BLOCKER)
Q4 – Not Done Yet (Spillover Candidates)¶
Purpose: Identify unfinished work
- Filters:
- Fixed version = Sprint 2025-03
- Status = New, Ready, In Progress, In Review, Blocked
- Saved as:
Sprint Close – Not done (spillover candidates)
Q5 – Spillover Missing Reason (BLOCKER)¶
Purpose: Enforce accountability
- Filters:
- Fixed version = Sprint 2025-03
- Status ≠ Done
- Spillover Reason = empty
- Rule:
This query must be empty
- Saved as:
Sprint Close – Spillover missing reason (BLOCKER)
Q6 – Blockers Snapshot¶
Purpose: Retro inputs
- Filters:
- Fixed version = Sprint 2025-03
- Status = Blocked
- Saved as:
Sprint Close – Blocked items snapshot
Updated by Redmine Admin about 2 months ago · 1 revisions