MI-03
Resolution Field Not Set on Closed Issues
Metric Integrity
Default severity: medium
MetricsQualityRisk
What it detects
Issues in configured Done statuses have no Resolution field value — Jira does not populate the Resolved date without a Resolution, making items invisible to all date-based cycle time reports.
Detection formula
IF issue.status IN config.workflow.done_statuses AND issue.resolution IS NULL OR issue.resolution = \'\' THEN FLAG metric_invisible Compute affected_count, pct_of_done_issues, estimated_metric_biasExamples in practice
- Items marked Done, no Resolution value — invisible to all cycle time tools
- Per issue
- Bulk admin transitions or resolution anomalies distort cycle time and velocity metrics.
Suggested response
Audit closure and field patterns so metrics reflect real completion, not bulk admin updates.
Coaching playbook
Symptom
Issues in configured Done statuses have no Resolution field value — Jira does not populate the Resolved date without a Resolution, making items invisible to all date-based cycle time reports.
Why it matters
When "Resolution Field Not Set on Closed Issues" 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
Audit closure and field patterns so metrics reflect real completion, not bulk admin updates.
Facilitation questions
- What system change would stop "Resolution Field Not Set on Closed Issues" 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.