Self-Assignment Rate by Project(5.3.8)

Self-assignment is not inherently wrong — in many teams it is a normal way for individuals to pick up available work. But a consistently high self-assignment rate may indicate that formal task allocation processes are being bypassed, that individuals are claiming ownership of issues to control their own workload visibility, or that access controls are too permissive.

What you can conclude

• A project where more than 60% of assignments are self-assignments may indicate that the formal allocation process is not being used — worth a process review.
• A very low self-assignment rate may indicate that managers are over-controlling task allocation — no one feels empowered to pick up work independently.
• Comparing self-assignment rates across projects reveals whether this is a team culture difference or a policy compliance gap.

How this chart works

Horizontal bar chart showing, per project, the percentage of assignee changes where the actor assigned the issue to themselves. The denominator is assignee changes only, not overall activity, so a busy project and a quiet one are directly comparable. Self-assignment is identified by the account id recorded on the change, never by a display name.

Projects with no assignee changes in the selected period are not charted. A missing bar means nobody reassigned anything, so there was nothing to measure; it does not mean allocation was reviewed and found healthy. The bar count therefore reflects how many projects had allocation activity, not how many projects exist. The number of assignee changes behind each bar is shown alongside it, so a rate resting on two changes can be told apart from one resting on ninety. Use the date and project filters to focus on specific teams or periods.