Priority and Assignee Drift by Project

When a ticket has its assignee or priority changed multiple times, it signals that something is unclear — who owns the work, how important it is, or both. Across a whole project, high drift rates on these fields point to planning instability that will show up in delivery risk.

What you can conclude

• High assignee drift in a single project often means ownership is unclear at planning — tickets are created without a clear owner and reassigned during execution.
• High priority drift suggests priorities are not well-calibrated at sprint planning.
• Projects with low drift scores are well-planned and well-owned.

How this chart works

Grouped bar chart showing per-project counts of assignee and priority changes, ranked by a composite drift score. Assignee changes are weighted at 1.5x to reflect the higher risk of ownership transfers. Projects ordered by drift score descending.