TI-14
Sub-Task Closed Long After Last Worklog
Time Tracking Integrity
Default severity: medium
EstimationProcessMetricsEffort
What it detects
Description is not yet published for this rule in the PRD catalogue.
Detection formula
No published identification formula is available yet for this rule.Examples in practice
- A team shows description is not yet published for this rule in the prd catalogue during analysis.
- Example signal: Description is not yet published for this rule in the PRD catalogue.
Suggested response
Fix time-tracking states so remaining, spent, and status align with reality.
Coaching playbook
Symptom
Description is not yet published for this rule in the PRD catalogue.
Why it matters
When "Sub-Task Closed Long After Last Worklog" 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 "Sub-Task Closed Long After Last Worklog" 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.