Configuration Change Event Audit Log

The charts above show patterns — this table shows the facts. Every configuration change is listed here with its date, event type, project, affected issue, and the actor who triggered it. It is the primary tool for forensic investigation and compliance review. During a NIS2, DORA, or GDPR audit, this is the log reviewers will ask to see.

What you can conclude

• Filter by actor to review all changes made by a specific administrator — useful for access reviews or investigating a suspicious event.
• Filter by event type to isolate destructive actions (deletions) and verify they were authorized and intentional.
• Filter by date range to scope the log to a specific audit period, sprint, or incident window.

How this chart works

Filterable audit table of all schema-level configuration events ordered by timestamp descending. Columns: date, event type (color-coded additive vs. destructive), project, issue key, triggering actor. Use date, project, field name, and actor filters to narrow the view.