DV-05
Mandatory Fields Missing at Stage Entry
Discipline
Default severity: medium
ProcessMetricsQuality
What it detects
An issue entered a workflow stage without all configured mandatory fields populated for that stage — the team proceeded without required planning inputs. Each stage has its own configurable set of mandatory fields.
Detection formula
FOR each_stage_transition(issue, from=S_prev, to=S_current): mandatory = config.discipline.mandatory_fields\[S_current\] // configurable per stage missing = \[f FOR f IN mandatory IF field_value(f, AT transition_date) IS EMPTY\] IF COUNT(missing) > 0 THEN FLAG Report: stage, missing_fields\[\], transition_date, actorExamples 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 entered a workflow stage without all configured mandatory fields populated for that stage 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 entered a workflow stage without all configured mandatory fields populated for that stage — the team proceeded without required planning inputs. Each stage has its own configurable set of mandatory fields.
Why it matters
When "Mandatory Fields Missing at Stage Entry" 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 Missing at Stage Entry" 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.