Actor Event-Type Specialization(4.5.6)

Different people naturally concentrate on different types of work: some focus on status transitions (execution), others on comments and updates (coordination), others on configuration changes (administration). This heatmap shows each actor's event-type distribution, making specialization patterns visible and helping leaders understand the team's operating structure.

What you can conclude

• An actor whose activity is almost entirely configuration changes may be in an admin role — or may be making unauthorized schema changes.
• An actor with a very narrow specialization profile is a single-point-of-failure for that type of work.
• A team where activity is evenly distributed across event types indicates a well-rounded, cross-functional team.

How this chart works

Heatmap showing each actor's distribution of event types as a percentage of their total events. Accounts Jira reports as apps, such as Automation for Jira, or as service-desk customers are left out; accounts Jira returned no type for stay in and are labeled unknown, and erased accounts stay in as erased. Each percentage is measured over the full retained event history, so this is an all-time specialization profile: the page's date range does not narrow this visual. Use the project and actor filters to focus on specific teams or individuals.