Event-Type Specialization by Actor

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 total events — 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 dominant activity type is "configuration changes" may have more access than their role requires.

What you can conclude

• Actors specialized in status transitions (above 60% of their activity) carry the highest SoD risk — they are the most likely to be involved in creator-equals-closer violations.
• Comment-heavy actors are typically reviewers or managers — low SoD risk, high collaboration value.
• Actors with a configuration-change-heavy profile should be verified as authorized Jira administrators.

How this chart works

Ranked table showing each actor's dominant event type, their top-action percentage, and a derived SoD risk label. Use the date and project filters to focus on specific teams or periods.