Actor Ownership Churn Ranking(2.5.9)

Ownership changes are a normal part of running work, and the people who triage make many of them. This visual separates three kinds of change each actor made: first assignments, reassignments from one person to another, and unassignments, where the actor cleared the assignee on an issue, whoever held it. A high unassignment count says the actor cleared many assignees, not that they gave up work of their own.

Actors are ranked by their Ownership Churn Score, which weights the three kinds differently so assigning work and clearing assignees can be told apart. It is not a performance judgment; it is a pattern surfacer.

What you can conclude

• An actor whose high score is dominated by initial assignments mostly gave issues with no assignee an owner, the pattern routine triage produces.
• For an actor with a high unassignment count relative to their assignments, a reviewer could ask whose assignees they cleared, and why.
• A team where churn is concentrated in one or two actors routes most of its ownership changes through those people.

How this chart works

Stacked horizontal bar chart ranking each actor by their Ownership Churn Score — a weighted metric combining initial assignments (×0.5), reassignments to others (×1.5), and unassignments (×2). Each bar is broken down by action type. 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.

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