MI-05
Admin Field Bulk Update on Closed Issues
Metric Integrity
Default severity: medium
MetricsQualityRisk
What it detects
A configured admin-only field was bulk-updated across more than the configured count of already-closed issues within a short time window — creates changelog noise.
Detection formula
admin_fields = config.mi.admin_bulk_monitored_fields // e.g. \[\'baseline_start\', \'baseline_end\'\] IF COUNT(updates to admin_fields, within config.mi.bulk_update_window_minutes) // default: 5min >= config.mi.bulk_update_min_count // default: 5 AND actor.role IN config.mi.admin_roles THEN LOG as admin_sweep — flag if issue is NOT in done_statusesExamples in practice
- Bulk admin transitions or resolution anomalies distort cycle time and velocity metrics.
- Closure timestamps or fields suggest data repair rather than organic delivery.
- A team shows a configured admin-only field was bulk-updated across more than the configured count of already-closed issues within a short time window while admin bulk monitored fields is set to Configured per workspace.
Suggested response
Audit closure and field patterns so metrics reflect real completion, not bulk admin updates.
Coaching playbook
Symptom
A configured admin-only field was bulk-updated across more than the configured count of already-closed issues within a short time window — creates changelog noise.
Why it matters
When "Admin Field Bulk Update 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 "Admin Field Bulk Update 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.