Compliance Event Canvas(5.8.1)

The Compliance Event Canvas brings every compliance-relevant event in your project history into one explorable view, so a reviewer can move fluidly between the big picture and a single incident during an audit session.

What you can conclude

• Whether control coverage stayed consistent across an audit window, such as a full quarter.
• Where notable spikes or unusual actor patterns warrant a closer look.
• Where activity gaps appear when measured against a control standard.
• How sprints move against their plan — surfaced in the sprint-drift category: sprints closed early or overrunning their planned end, dates or names changed mid-flight, scope added after a sprint started, or a sprint started by one person and closed by another.
• Whether issue ownership stays stable — surfaced in the assignee-churn category: an issue passed between owners repeatedly, or an assignee removed entirely, which makes the record of who owned the work harder to follow.
• Whether closed work stays closed — surfaced in the reopen-after-close category: an issue moved back to an active status after being marked done, closed, or resolved, which can signal premature sign-off or unstable resolution.

How this chart works

The canvas plots events on a zoomable surface you can filter by actor, type, time, and category — workflow drift, sprint-governance drift, assignee churn, reopen-after-close, configuration changes, PII detections, and more — letting you narrow from a wide audit window down to a single project. It pairs naturally with the Workflow Drift Stream for follow-up on specific drift incidents.

When a person's Atlassian account has been erased, the events they took part in stay on the canvas without an actor, and a summary that named them shows "erased account" in their place. Each event also carries the type of account Jira reports for its actor: person, app (such as Automation for Jira), customer, unknown when Jira returned no type, erased, or system when no actor was recorded. An action Jira records under a person's account counts as that person's, even when a tool acted on their behalf.