Rubber-stamp issues(5.2.4)

Closures into a delivered status within five minutes of the issue being created, which MetaFrazo calls rubber-stamp closures; the name describes the timing, not anyone's intent or whether a review happened elsewhere. The count covers closures made by people; fast closures by apps such as Automation for Jira, by service-desk customers, by accounts Jira returned no type for, by erased accounts or with no recorded actor are shown beside it. Counted over closures into delivered statuses only, under your organization's terminal-status settings (a MetaFrazo default applies until configured); fast discards are backlog hygiene and are not counted. This total covers every week in the selected range, including the week in progress. Weeks are counted whole: a week that falls only partly inside the selected range is not included. The Fast-Close Distribution chart below it covers the same weeks.