Event Volume by Actor(5.6.5)

This visual maps the complete activity profile of every actor in your Jira instance — how much they do and what types of actions they take. An actor who is 80% status transitions is primarily executing work. An actor whose bar is mostly assignee and priority changes is routing or reprioritizing work rather than executing it, which may fit a coordinator or an admin, or may point to access the role was not meant to cover. The breakdown makes those patterns visible.

What you can conclude

• For an actor whose profile is concentrated in status transitions (above 70%), a reviewer could ask whether the same account appears on the Workflow manipulation pages.
• An actor with a mix of event types (transitions, comments, assignee and priority changes) works across several kinds of action.
• For an actor with almost no activity, the question is whether the account still needs its access.
• An account Jira reports as an app, such as Automation for Jira, is labeled as one, by Jira's own record. An action recorded under a person's account counts as that person's, even when a tool acted under their credentials.

How this chart works

Stacked bar chart with one bar per actor and four segments: status transition, assignee change, priority change and comment event. Each segment counts a Jira change once, even where Jira reports the same change through two events, as it does when an assignment is made together with another edit. Events outside those four types are not drawn; they count toward the actor's total, which only decides the order of the bars. Use the date and project filters to focus on specific teams or periods. Each bar is labeled with the type of account Jira reports for the actor: person, app, customer, unknown when Jira returned no type, or erased.