Top Solo-Close Actors(5.2.10)

When solo closes concentrate in a few people, the concentration can have an ordinary explanation, such as a role whose work is to open and close its own issues. This table lists the actors with the highest counts of solo closes, delivered closures where the person who closed the issue also created it, so questions can go to the people and projects involved rather than to the whole team.

What you can conclude

• An actor with a high solo-close count and a high solo-close percentage closes most of their delivered work on issues they created themselves. A reviewer could ask how review works for those issues and whether the actor's role explains the pattern.
• An actor with a high absolute count but a low percentage may just be very active — context matters.
• A table with no actor in the Critical or High tier means no single person accounts for many solo closes in the selected period.

How this chart works

Ranked table showing actors by count of solo closures (creator = closer), their solo-close percentage of closures with an attributable creator, their primary project, and a risk tier label. The tier is MetaFrazo's band for the solo-close count: Critical at 20 or more, High at 10 to 19, Medium at 5 to 9, and Low below 5. Counts and percentages cover delivered closures only; discards are backlog hygiene and are not counted, and an actor whose closures carry no attribution evidence shows no count rather than a zero. Each actor carries the type of account Jira reports for it (person, app, customer, unknown or erased); tiers rank people's accounts, and other accounts are listed with their type rather than ranked as people. Use the date and project filters to focus on specific periods.

Teams preparing a DORA or NIS2 review use this to identify who to ask about first.