Single-Actor Resolution Rate(5.2.6)

A solo close is MetaFrazo's name for a delivered closure where the person who moved the issue into a done status is the same person who created it. The measure compares those two people and no one else: it does not show whether another actor commented on, reviewed or worked the issue in between, and a review recorded outside Jira is not visible to it. This visual tracks how often solo closes occur week by week, so you can see whether their share of delivered closures is rising or falling.

Each closure is attributed to the type of account that made it, as Jira reports it. The rate covers closures made by people's accounts; an app account such as Automation for Jira that closes issues it created is recorded as app activity and shown beside the rate, not inside it, and closures by service-desk customers and by accounts Jira returned no type for are shown the same way. A closure made by an account that has since been erased carries no closer and is not counted. An action Jira records under a person's account counts as that person's, even when a tool acted on their behalf.

What you can conclude

• A solo-close rate that rises over several weeks means a growing share of delivered work is closed by the person who created it. A reviewer could ask which roles and projects account for the rise, and whether closing one's own work is expected there.
• A falling rate means a growing share of delivered closures are made by someone other than the creator; it does not show what, if anything, that second person reviewed.
• Some roles routinely close their own issues, so a steady rate is best read against how the team divides creating and closing work.

How this chart works

Weekly dual-line chart showing the percentage of delivered closures where the creator also closed the issue (solo close) versus closures involving a different actor. Closures into abandoned-classified statuses are backlog hygiene and are not counted, and a closure whose creator cannot be attributed is excluded from both sides of the rate rather than presented as peer-validated. Use the date and project filters to focus on specific teams or periods.

For teams preparing a DORA or NIS2 review, reviewers typically ask how often the person who created a piece of work also closed it; this chart is the portfolio-level view of that question.

The week in progress is shown at its value so far. Because the week is not yet complete, it covers only the issues delivered so far and can move in either direction as the week closes. A week that falls only partly inside the selected date range is not drawn, so this chart can show fewer weeks than the range spans. This applies at both ends of the range, apart from the week in progress, and a caption under the chart names the week that is not included.