DV-09

Missing Due Date on Time-Sensitive Issue Type

Discipline

Default severity: medium
ProcessMetricsQuality

What it detects

An issue of a configured time-sensitive type (compliance, security, deadline-driven) has no due date or target date set.

Detection formula

time_sensitive_types = config.discipline.due_date_required_types // configurable per org date_fields = config.content.target_date_fields IF issue.type IN time_sensitive_types AND ALL(field_value(f) IS NULL FOR f IN date_fields) THEN FLAG

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 of a configured time-sensitive type (compliance, security, deadline-driven) has no due date or target date set while due date required types 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 of a configured time-sensitive type (compliance, security, deadline-driven) has no due date or target date set.

Why it matters

When "Missing Due Date on Time-Sensitive Issue Type" 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 Due Date on Time-Sensitive Issue Type" 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.

Product tourSign in
DV-09: Missing Due Date on Time-Sensitive Issue Type — FlowAnalyzer