TI-04
Done Issue with Time Remaining \> 0
Time Tracking Integrity
Default severity: medium
EstimationProcessMetricsEffort
What it detects
An issue in a Done/Resolved/Closed status still has a positive time remaining value — the issue was closed before all planned work was completed according to the estimate. Either the estimate was overcalculated, the work was genuinely incomplete, or the remaining time was never cleared after closure.
Detection formula
IF issue.status IN config.workflow.done_statuses AND issue.time_remaining > 0 THEN FLAG done_with_remaining IF issue.time_remaining > issue.original_estimate * config.ti.significant_remaining_pct // default: 0.20 (20% of estimate still remaining) THEN CRITICAL — substantial planned work not completed at closure Report: issue, time_remaining, original_estimate, time_spent, remaining_pct Impact: original estimate is overcounted in completion reports; capacity model inflatedExamples in practice
- A team shows an issue in a done/resolved/closed status still has a positive time remaining value while done statuses is set to Configured per workspace.
- Example signal: An issue in a Done/Resolved/Closed status still has a positive time remaining value — the issue was closed before all planned work was completed according to the estimate.
Suggested response
Fix time-tracking states so remaining, spent, and status align with reality.
Coaching playbook
Symptom
An issue in a Done/Resolved/Closed status still has a positive time remaining value — the issue was closed before all planned work was completed according to the estimate. Either the estimate was overcalculated, the work was genuinely incomplete, or the remaining time was never cleared after closure.
Why it matters
When "Done Issue with Time Remaining \> 0" 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 Time Remaining \> 0" 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.