Weekly Activity Density by Project(4.1.6)

Activity volume is not a measure of productivity, but it does show where work is being recorded. When a project suddenly goes quiet, the events show that it stopped, not why: a reviewer could ask whether the team moved to other work, whether the work is blocked, or whether the project's priority changed, and whether that was a recorded decision. This heatmap makes those changes visible across the entire portfolio.

What you can conclude

• A project whose weeks go from busy to quiet without a known explanation raises the question of what changed.
• Comparing activity density across projects in the same portfolio shows where work is being recorded, which a reviewer can set against where the plan puts it.
• Consistently high activity in a project that is also showing low quality scores is a combination worth a question: what is driving both?

How this chart works

Heatmap showing raw event counts per project per ISO week. Each cell's shade follows the legend, from low to high activity. Each cell's events are also counted by the type of account Jira reports (person, app, customer, unknown when Jira returned no type, erased, or system when no actor was recorded), with people's events as the headline and the others beside them, never inside them. A week in which a project's only recorded events were its own creation, change, archiving, unarchiving, trash, restore or deletion has no cell: those events describe the project rather than work in it. Use the date and project filters to set the observation window.

The week in progress is not counted: the heatmap draws complete weeks only, and a project with no complete week in the selected range has no row.