DV-03
Worklog Not Updated in Active Issue
Discipline
Default severity: medium
ProcessMetricsQuality
What it detects
An issue in an active status has had no time logged for longer than the configured inactivity threshold — work may be happening but is not recorded, making effort tracking and retrospectives impossible. last_worklog = MAX(worklog.date) per issue
Detection formula
worklog_gap = config.discipline.worklog_gap_days // default: 3d IF issue.status IN config.workflow.active_statuses AND (today - last_worklog) > worklog_gap AND issue.type IN config.discipline.worklog_required_types // configurable THEN FLAGExamples 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 an active status has had no time logged for longer than the configured inactivity threshold while worklog gap days is set to 3d.
Suggested response
Enforce assignee, field, hierarchy, and sprint hygiene rules your team agreed on.
Coaching playbook
Symptom
An issue in an active status has had no time logged for longer than the configured inactivity threshold — work may be happening but is not recorded, making effort tracking and retrospectives impossible. last_worklog = MAX(worklog.date) per issue
Why it matters
When "Worklog Not Updated in 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 "Worklog Not Updated in 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.