DV-32
Weak Continuous Update Cadence on Active Issue
Discipline
Default severity: medium
ProcessMetricsQuality
What it detects
Description is not yet published for this rule in the PRD catalogue.
Detection formula
No published identification formula is available yet for this rule.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 description is not yet published for this rule in the prd catalogue during analysis.
Suggested response
Enforce assignee, field, hierarchy, and sprint hygiene rules your team agreed on.
Coaching playbook
Symptom
Description is not yet published for this rule in the PRD catalogue.
Why it matters
When "Weak Continuous Update Cadence on Active Issue" 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 "Weak Continuous Update Cadence on Active Issue" 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.