Batch Close Detection

Closing two or more distinct issues within a 30-minute window is a potential batch close — an actor processing multiple tickets rapidly without genuinely engaging with each one. At low volumes, this may simply reflect an efficient review session. At high volumes, particularly for critical or high-priority issues, it suggests that individual issues are not receiving appropriate attention.

What you can conclude

• Critical-tier batch closes (5 or more issues in 30 minutes) warrant investigation — was each issue genuinely reviewed before closure?
• Medium-tier events (2–4 issues in 30 minutes) are worth monitoring but may be legitimate efficient review sessions.
• A clean log with no batch close events indicates that issues are being closed individually with appropriate attention.

How this chart works

Alert log showing actors who closed multiple distinct issues within a 30-minute window, with severity classification: Medium (2 issues), High (3–4), Critical (5+). Use the date, project, and batch severity filters to scope the investigation.