TI-05
Done Issue with Zero Time Spent
Time Tracking Integrity
Default severity: medium
EstimationProcessMetricsEffort
What it detects
An issue was resolved/closed with zero hours logged — it was completed with no recorded work. Either the issue was done trivially (and should have been minimal SP), done before logging was set up, or closed incorrectly without real work. Distinct from SG-04 by including pre-release and closed stages.
Detection formula
IF issue.status IN config.workflow.done_statuses AND SUM(worklog.time_spent, issue) = 0 AND issue.story_points > config.ti.sp_requires_worklog_min // default: 1 SP THEN FLAG done_zero_spend IF issue.story_points >= config.ti.critical_sp_zero_spend // default: 5 SP THEN CRITICAL — 5+ SP issue closed with no work evidence Correlate with MI-03 (resolution field not set) and OI-01 (operational tracker)Examples in practice
- A team shows an issue was resolved/closed with zero hours logged while done statuses is set to Configured per workspace.
- Example signal: An issue was resolved/closed with zero hours logged — it was completed with no recorded work.
Suggested response
Fix time-tracking states so remaining, spent, and status align with reality.
Coaching playbook
Symptom
An issue was resolved/closed with zero hours logged — it was completed with no recorded work. Either the issue was done trivially (and should have been minimal SP), done before logging was set up, or closed incorrectly without real work. Distinct from SG-04 by including pre-release and closed stages.
Why it matters
When "Done Issue with Zero Time Spent" 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
Fix time-tracking states so remaining, spent, and status align with reality.
Facilitation questions
- What system change would stop "Done Issue with Zero Time Spent" 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.