Drift Score by Actor(JIRA:4.3.10)

Visual
Where to find it:JiraComplianceActor drift
Advanced edition
Open in dashboard

Rather than requiring a compliance investigator to correlate three separate signals per actor by hand, this table aggregates them into a single score. Actors with high scores carry a large total from the three signals (reporter changes, multi-project activity and self-assignment), whether from one of them or several: reporter changes alone can pass 70, while the other two together reach at most 60.

What you can conclude

  • Actors with scores of 70 or above are flagged as high risk; the table's signal columns show whether one signal or several make up the score.
  • Actors in the 40–69 range sit below the 70-point high-risk band.
  • Actors below 40 have a low combined score, though one signal on its own can still be present.

How this chart works

Ranked table showing actors with a composite drift score (0 to 100), built from three signals measured per actor per week: reporter changes, the number of distinct projects the actor was active in, and their self-assignment rate. Color-coded: red (70 or above), amber (40 to 69), green (below 40).

The self-assignment term uses the same definition as the Self-Assignment Rate by Project chart on this page: self-assignments divided by assignee changes, not by overall edit volume. That rate is shown in the table next to the number of assignee changes it was measured over, so a rate resting on two changes can be told apart from one resting on ninety. An actor who made no assignee changes at all in the week shows a blank rate and contributes nothing to this term; the rest of their score still reflects the other two signals. The self-assignment term only enters the score once the actor made at least five assignee changes in the week; below that the rate is still shown, contributes nothing, and the table says whether it was scored. Use the date and project filters to focus on specific periods. Each actor carries the type of account Jira reports for it: person, app, customer, unknown when Jira returned no type, or erased.

Who sees this panel: it shows individual accounts, so it appears only after an organization owner turns on "Show person-level views" in Organizational Settings, and then only to owners and admins. With the setting off, or for auditors and users, the panel, its export and its AI analysis withhold the per-account rows, and the panel shows a notice in its place rather than an empty chart; the team and project panels on the page are unchanged. Every change of the setting is recorded in the settings audit log with who changed it and when.