Fast-Close Distribution(5.2.8)

An issue closed as delivered within 5 minutes of being created spent almost no time open in Jira: it was created and closed almost at once. The work may have been done before the ticket existed, done elsewhere, or not done; the events cannot tell these apart. This histogram shows the distribution of time-to-close so you can see how many closures fall into the sub-5-minute bucket.

What you can conclude

• A significant number of issues in the under-5-minute bucket means tickets are routinely created and closed almost at once, and a reviewer could ask where that work is planned and reviewed.
• Issues in the 5–30 minute bucket warrant review — they may represent genuinely quick tasks, or may be fast-closed without adequate verification.
• A distribution skewed toward the 24+ hour bucket means most work spends at least a day open in Jira.

How this chart works

Histogram showing the distribution of time between issue creation and closure across five buckets: under 5 minutes, 5–30 minutes, 30 minutes to 2 hours, 2–24 hours, and over 24 hours. Delivered closures in the under-5-minute bucket are flagged as rubber-stamps; abandoned-destination closures appear in the distribution with their own disposition and are excluded from the flag. Each bucket is also split by the type of account that closed the issue (person, app, customer, unknown, erased, or system where no actor was recorded); the flag counts people's closures, and the types add up to each bucket.

Each bar covers every week in the selected range, including the week in progress.