Issue Reassignment Hotspot Leaderboard

Some tickets get passed around repeatedly without anyone taking definitive ownership. Each reassignment adds delay, context loss, and confusion. This leaderboard surfaces the tickets with the highest reassignment count so they can be investigated directly.

A ticket that has been reassigned five or six times is not just inconvenient — it usually points to something deeper: unclear requirements, an unacknowledged dependency, or a task that no one wants to take responsibility for. Understanding why helps break the cycle.

What you can conclude

• Tickets at the top of this list with High badges (3+ reassignments) are candidates for a direct conversation — why hasn’t anyone committed to owning this to completion?
• If multiple hotspot tickets belong to the same epic or project area, the problem may be at the requirement or scoping level.
• All-unowned hotspot tickets (NULL current assignee) are the highest priority — they are stuck with no current responsible party.

How this chart works

Ranked horizontal bar chart of issues by total assignee-change count. Color-coded volatility badge: High (≥ 3 events), Medium (= 2), Low (= 1). Also shows the current assignee — NULL means currently unowned.

Use the minimum reassignments filter to focus on the most critical cases only.