Event-Type Specialization by Actor(5.6.10)

This table provides a clean summary of each actor's dominant activity type — the single action type that accounts for the largest share of their status transitions, comments and assignment changes taken together — alongside a derived SoD risk label. It is designed for role-based access reviews: comparing what people are actually doing against what their assigned role should permit.

An actor whose role is "developer" but whose activity is almost entirely status transitions is worth checking against what that role is meant to cover.

What you can conclude

• Actors specialized in status transitions -- above 60% of their status transitions, comments and assignment changes taken together -- carry the highest SoD risk, and are the ones most likely to also appear in the Segregation of Duties Violations panel, where creator-equals-closer is measured directly. Reads of an issue, worklogs, attachments, links and administrative actions are not part of that share: they say nothing about who moved the work.
• Comment-heavy actors are typically reviewers or managers — low SoD risk, high collaboration value.
• Actors with an assignment-heavy profile are typically coordinators or triage owners; confirm that routing work is part of the role.

How this chart works

Ranked table showing each actor's dominant workflow action, that action's share of their status transitions, comments and assignment changes, the number of workflow actions behind the share, their total event count (each Jira change counted once, even where Jira reported it through two events), and a derived SoD risk label. An actor whose events are entirely reads, worklogs or administration has no workflow actions and is shown as such rather than being scored. Use the date and project filters to focus on specific teams or periods.