Screen reference
Audit log
Who changed what, and when: a chained history where any modification shows when you verify.
What the screen is for
The screen lets you filter the log, verify its integrity and export it to CSV. The audit pack is generated from the Audit pack page.
Who can do what
The log names people and keeps every change. It is therefore not open to everyone.
| Action | Reader | Compliance manager | Jira administrator | Auditor |
|---|---|---|---|---|
| Read the log, verify it, export it | no | yes | yes | yes |
A reader sees "The journal is not open to your profile". The auditor role holds this right for the length of its dated grant.
Step by step
Read and filter
- Filter by "Type of object", "Action", "Actor" and by period ("Du", "Au"). "Reset" clears the filters.
- Each line gives the "Date", the "Acteur", the "Action" and the "Object", with its sequence number.
- "Show older entries" loads the rest.
- An actor can be a person, the "System" (the daily run), the "AI assistant" or an "Auditor". An account no longer found in the Atlassian directory is shown as "Unknown account". If the directory does not answer, names are replaced by the end of the account identifier.
Verify integrity
- Under "Journal integrity", click "Verify the integrity".
- The app recomputes each entry and compares it with the fingerprint of the next one.
- The result is either "Log intact", with the number of entries verified, or "Log tampered at entry no. N", with the reason: malformed entry, missing entry, changed order, changed content, end of the log removed, and so on.
- "Verify again" starts again.
Export to CSV
- Choose the period and the filters.
- Click "Export as CSV". An export holds at most 2,000 entries (the most recent of the selection) and 3 MB. If the export is capped, the screen says so: narrow the period to get the older ones.
- The file
journal-audit-YYYY-MM-DD.csvcontains, among other things, the fingerprints of each entry.
What the auditor will take from it
- A history that is visibly tamper-evident: if someone changes, removes or reorders an entry, the verification shows it.
Known limits
- Integrity proves that the history has not been altered since it was written. It does not prove that a recorded action was right.
- The log is not rewritten when an Atlassian account is closed: the name is replaced by "Closed account", but the identifier stays (see Security and privacy).
- The report reproduces the latest 200 log entries; the CSV file is complete.
Was this page helpful?