Repeat Reopener Actor Fingerprint(2.3.7)

Reopening a ticket is not inherently wrong — but when the same actor is responsible for the majority of reopens across many tickets, it becomes a signal worth investigating. It may indicate a pattern of premature closure, a habit of bypassing review, or a misunderstanding of what "done" means in this team's context.

This view does not assign blame — it surfaces a pattern. The right response is a conversation, not a disciplinary measure.

What you can conclude

• A single actor accounting for the majority of all reopens is a clear signal that something in their workflow or understanding of done needs attention.
• If reopens are spread evenly across many actors, the problem is likely process-wide rather than individual.
• Cross-reference with the Most-Reopened Issues Leaderboard to see whether a specific actor is repeatedly reopening the same tickets.
• Where the actor is an app account by Jira's own record, such as Automation for Jira, its reopens are counted as the app's, and the question is what sets that app off.

How this chart works

Donut chart with one slice per actor who triggered a reopen, sized by that actor's reopen count and labeled with the count and its share of all reopens. The legend shows each actor's eight-character id, and hovering a slice shows the full id. Each actor is labeled with its type as Jira reports it: person, app, customer, unknown when Jira returned no type, erased, or system when no actor was recorded. The number of distinct issues each actor reopened is not drawn; it is passed to Deep Analysis.

Use the date and project filters to focus on a specific period or team.