Team Engagement & Activity Mix(2.1.9)

Not all activity is equal. A team can be very busy in Jira — commenting, updating fields, logging time — while tickets barely move forward. This visual breaks down the mix of activity types so you can see how much of the recorded activity was issue updates, which carry status changes, and how much went into the discussion, time logging and other work around them.

A high ratio of comments to issue updates, for example, raises the question of whether the requirements are clear.

What you can conclude

• Where issue updates are the largest type, the type that carries status changes outnumbers every other kind of recorded activity.
• Where comments are high relative to issue updates, a reviewer could ask whether the scope is clear, or whether the work is waiting on something.
• Where worklog entries are few beside a high issue-update volume, the question is whether time is logged for that work.

How this chart works

Chart of the Jira events recorded for your site by event type (issue creations and updates, comments, worklog entries, assignments, attachments, sprint and board changes, and others). Each type's actions are a bar on the left axis, and the number of distinct accounts behind each type is a line on its own Accounts axis at the right: account counts are far smaller than action counts and would not be readable on the same scale. The actions are split 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 actions as the headline and the others counted beside them, never inside them; the account lines show people's accounts (solid) beside all accounts (dashed). A status change arrives as an issue update and is counted there, not separately. MetaFrazo's own instrumentation records are not Jira events and are not counted. Events with no recorded person behind them, such as field or project configuration changes and user-account changes (whose events name only the account they are about), count as actions and add no contributor. The chart covers the whole recorded history; the page's date and project filters do not narrow it.

The actor filter does not apply to this chart; the account count for each type shows how many distinct accounts produced it, people's counted apart.