DV-06
Mandatory Fields Still Empty in Current Status
Discipline
Default severity: medium
ProcessMetricsQuality
What it detects
An issue in its current status is missing one or more fields that are configured as mandatory for that status — the gap has not been retroactively filled since stage entry.
Detection formula
mandatory_now = config.discipline.mandatory_fields\[issue.status\] missing_now = \[f FOR f IN mandatory_now IF field_value(f) IS EMPTY\] IF COUNT(missing_now) > 0 THEN FLAG Compute: days_missing = today - date_entered_current_status Severity escalates with days_missingExamples 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 in its current status is missing one or more fields that are configured as mandatory for that status while mandatory fields is set to Map configured per issue type.
Suggested response
Enforce assignee, field, hierarchy, and sprint hygiene rules your team agreed on.
Coaching playbook
Symptom
An issue in its current status is missing one or more fields that are configured as mandatory for that status — the gap has not been retroactively filled since stage entry.
Why it matters
When "Mandatory Fields Still Empty in Current Status" 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 "Mandatory Fields Still Empty in Current Status" 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.