DV-08
Missing Labels or Tags
Discipline
Default severity: medium
ProcessMetricsQuality
What it detects
An issue of a configured type is missing configured mandatory labels or tag categories — prevents filtering, reporting, and team-based aggregation in flow metrics.
Detection formula
required_label_categories = config.discipline.required_label_categories // e.g. \[\'team\', \'domain\', \'initiative\'\] FOR each_category C IN required_label_categories: IF COUNT(issue.labels WHERE label IN config.discipline.labels\[C\]) = 0 THEN FLAG missing_category CExamples 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 of a configured type is missing configured mandatory labels or tag categories while required label categories is set to \[\].
Suggested response
Enforce assignee, field, hierarchy, and sprint hygiene rules your team agreed on.
Coaching playbook
Symptom
An issue of a configured type is missing configured mandatory labels or tag categories — prevents filtering, reporting, and team-based aggregation in flow metrics.
Why it matters
When "Missing Labels or Tags" 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 "Missing Labels or Tags" 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.