Reassignment Frequency Heatmap(2.5.5)

Not all reassignments are equal. Some happen at sprint kickoff when work gets distributed. Others happen mid-week when blockers surface. This visual shows you when reassignments are concentrated — so you can tell the difference between planned triage and reactive firefighting.

A Monday spike often reflects sprint planning reassignments. A Friday spike may signal scope-shedding before the weekend. A mid-week surge usually points to a blocker, escalation, or team reshuffle.

What you can conclude

• Consistent Monday peaks are normal and indicate planned sprint triage — not a governance concern.
• Spikes on unexpected days (mid-sprint, weekends) warrant investigation — something disrupted normal workflow.
• Weeks with near-zero activity are baseline periods — useful for calibrating what “normal” looks like for your team.

How this chart works

Stacked bar chart showing weekly reassignment counts, color-coded by day of week. Each stack is one week, broken down by the days on which reassignments occurred. A reassignment here is one logical change of owner from one person to another — Jira records each change under two event types, and both are collapsed into one; handing work to someone for the first time (an initial assignment) and removing an owner (an unassignment) are counted separately and shown alongside.

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