DV-15
Rolled Over Issue Not Flagged
Discipline
Default severity: medium
ProcessMetricsQuality
What it detects
An issue was carried from one sprint to the next without being flagged as an impediment — the team acknowledged the carryover without formally signalling why. Repeat carryovers without flags indicate normalised non-delivery. sprint_rollovers = COUNT(sprints WHERE issue was present but not Done AT sprint.end)
Detection formula
IF sprint_rollovers >= config.discipline.rollover_flag_threshold // default: 2 AND COUNT(flag_events DURING rollover_sprints) = 0 THEN FLAG unacknowledged_rollover IF sprint_rollovers >= config.discipline.critical_rollover_count // default: 3 THEN CRITICALExamples in practice
- Assignee, field, hierarchy, or sprint hygiene rules are violated on active work.
- Issues miss mandatory fields or ownership while still in progress.
- A team shows an issue was carried from one sprint to the next without being flagged as an impediment while rollover flag threshold is set to 2.
Suggested response
Enforce assignee, field, hierarchy, and sprint hygiene rules your team agreed on.
Coaching playbook
Symptom
An issue was carried from one sprint to the next without being flagged as an impediment — the team acknowledged the carryover without formally signalling why. Repeat carryovers without flags indicate normalised non-delivery. sprint_rollovers = COUNT(sprints WHERE issue was present but not Done AT sprint.end)
Why it matters
When "Rolled Over Issue Not Flagged" keeps appearing, the team is signalling a repeatable process gap. Left unexamined, the pattern hides where work really stalls and makes improvement metrics harder to trust.
What you can achieve
Enforce assignee, field, hierarchy, and sprint hygiene rules your team agreed on.
Facilitation questions
- What system change would stop "Rolled Over Issue Not Flagged" from firing again?
- What do the cited issues have in common — same root cause or same workaround?
- Who owns the two-week experiment and how will we verify on the next import?
Run this rule against your own tracker data with Flow Analyzer.