DV-14
Issue Not Updated During Its Sprint
Discipline
Default severity: medium
ProcessMetricsQuality
What it detects
An issue was in an active sprint for the full sprint duration but received no status transition — it was planned but neither progressed nor removed from scope. Silent non-delivery.
Detection formula
IF issue IN sprint AND COUNT(status_transitions, date BETWEEN sprint.start AND sprint.end) = 0 AND issue.status NOT IN config.workflow.done_statuses AT sprint.end THEN FLAG silent_non_delivery Differentiate: was it carried to next sprint or silently left?Examples 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 in an active sprint for the full sprint duration but received no status transition while done statuses is set to Configured per workspace.
Suggested response
Enforce assignee, field, hierarchy, and sprint hygiene rules your team agreed on.
Coaching playbook
Symptom
An issue was in an active sprint for the full sprint duration but received no status transition — it was planned but neither progressed nor removed from scope. Silent non-delivery.
Why it matters
When "Issue Not Updated During Its Sprint" 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 "Issue Not Updated During Its Sprint" 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.