Hourly Activity Density(5.6.9)

This heatmap shows the normal working rhythm of the team — the hours and days when Jira activity is concentrated. It establishes the baseline that makes off-hours anomalies visible. A team working 9-to-5 Monday to Friday will show a very different pattern from a globally distributed team, and both are valid.

Understanding the normal pattern is the prerequisite for identifying deviations from it.

What you can conclude

• A dense cluster in standard business hours for a single timezone indicates a co-located team with predictable working hours.
• Activity spread across all hours suggests a globally distributed team — off-hours anomaly detection is calibrated to the organization's time zone, so a broad spread reflects genuinely distributed working rather than an artifact of where the clock is set.
• A sudden change in the density pattern (previously quiet evenings becoming active) may indicate a team change, a new app account, or unauthorized access; the account types in each cell show whether an app account is behind it.

How this chart works

Heatmap showing total event volume per hour of day (x-axis, in the organization's time zone) × day of week (y-axis). Darker cells indicate higher total activity. Use the date and project filters to build the baseline for a specific team. Each cell's count is split by the type of account Jira reports (person, app, customer, unknown when Jira returned no type, or erased): people's events form the headline and the others are counted beside them, never inside them.

Only complete weeks are counted: a week still in progress, or one the selected date range cuts through, is left out entirely so that every cell is measured over the same number of weeks.