Self-Assignment Rate by Project(5.3.8)

Visual
Where to find it:CompliancePermission drift
Ent Standard
Open in dashboard

Self-assignment is not inherently wrong — in many teams it is a normal way for individuals to pick up available work. A consistently high self-assignment rate raises questions a reviewer could ask: is there a formal allocation step, is it used, and who is able to assign work to themselves?

What you can conclude

  • In a project where more than 60% of people's assignee changes are self-assignments, the question is whether a formal allocation step exists and whether it is used.
  • A very low self-assignment rate means most work is assigned by someone other than the person it is assigned to.
  • Comparing self-assignment rates across projects reveals whether this is a team culture difference or a difference in how approval is configured.
  • 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.

How this chart works

Horizontal bar chart showing, per project, the percentage of assignee changes where the actor assigned the issue to themselves. Both the count and the denominator cover assignee changes made by people's accounts, as Jira reports the account type: an automation rule that assigns issues would otherwise pull a project's rate down, so changes by apps, service-desk customers and accounts Jira returned no type for are shown beside the bar instead. A project whose assignee changes were all made by other accounts has no people's rate and is shown without one. 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. Use the date and project filters to focus on specific teams or periods.