Blog ·
Jira audit log: what it records, and how to review it
The Jira audit log is a record of configuration changes on your Jira site: permission schemes edited, workflows published, fields made required, users added to groups or roles, work items deleted. A Jira administrator finds it under Settings, then System, then Audit Log. A second, wider audit log lives in Atlassian Administration and covers the organization: accounts, security policies, and app access. Neither one records everything, and neither one reviews itself. This guide covers what each log holds, how long it keeps events, how to export it, and how to turn "someone should look at the audit log" into a review that arrives on a schedule.
Statements about Atlassian's audit logs are as of October 2026, read from Atlassian's own support documentation. Features and retention can differ by plan, so check your own site before you rely on a figure.
Two audit logs, two scopes #
People searching for the Jira audit log usually mean one of two places, and they answer different questions.
| Jira audit log | Organization audit log | |
|---|---|---|
| Where | Jira: Settings, System, Audit Log | Atlassian Administration: Insights, Audit log |
| Who can open it | Users with the Administer Jira global permission | Organization admins and site admins |
| What it covers | Configuration changes inside Jira | Organization activity: accounts, groups, security settings, app access |
| Export | CSV, up to 100,000 events | CSV by email, up to 10,000 activities from the past 180 days |
| Typical question | Who changed this workflow? | Who gave this person access? |
If something changed inside a Jira project, start with the Jira audit log. If the question is about an account, a login policy or which apps a person can reach, the organization log is the one to open.
What the Jira audit log records #
Atlassian's page on audit activities in Jira states the purpose plainly:
The audit log is intended to record configuration changes that can impact users and spaces.
Its table of captured events, as of October 2026, groups them into categories. In short:
- Space changes: a space created, removed or updated. (Atlassian now calls projects "spaces" in much of its documentation.)
- Permission changes: permission schemes created, edited or assigned, and global permissions added to or removed from a group.
- Workflow changes: workflows created, copied, renamed or removed, drafts published, statuses created or updated, and workflow schemes changed.
- Notification, screen and field changes: notification schemes, screens and tabs, custom fields, screen schemes and field schemes, including a field switched between required and optional.
- Work type changes: work types and work type schemes created, updated or deleted.
- Plan and sprint changes: plans created or updated, and sprints created, started, updated, closed or deleted.
- Work item deletion: tracked by the work item number.
Two practical uses follow from that list. When a field suddenly becomes mandatory or a transition vanishes, the log tells you who changed the scheme and when. And when a ticket seems to have disappeared, searching the log for "work item deleted" or the item's key shows whether it was deleted, by whom and at what time.
What it does not record #
Atlassian is direct about the limits:
The audit log isn't intended to record all activity in Jira.
It is not an activity feed. Edits to a ticket's summary, comments and status changes live in each work item's own history, not in the audit log. A few other gaps are worth knowing before you depend on it:
- It isn't available on the Free plan. Atlassian's page says the audit log isn't available if all of your Jira Cloud apps are on the Free plan.
- You can't sort it in the page. Atlassian's suggestion is to export to CSV and sort in a spreadsheet.
- Some user management changes show no author. Atlassian lists a known issue where changes made in the user management pages, such as users being created or added to groups, don't display the username of the person who made the change.
- Events before August 2024 may be missing. Atlassian notes improvements released then, and some earlier events may not appear.
- A deleted work item stays deleted. The log proves the deletion happened; it cannot bring the item back. Our Jira backup guide covers the restore side.
How long events are kept #
Retention is set in the log itself. In the Jira audit log, select Actions, then Audit Log Settings, choose a retention period such as 6 months, and save. The same screen controls whether events from external user directories like LDAP appear.
The organization log follows your plan. As of October 2026, Atlassian's documentation says organization audit log activity is available for 180 days without an Atlassian Guard subscription, and for 365 days with one. Which app-level events you can see there also depends on your plans, and Atlassian publishes a comparison table for each app.
Retention is the reason a regular export matters. If your auditor asks about a change from 14 months ago and your log only keeps 6, the event is gone unless someone saved it.
How to export the Jira audit log #
From the Jira audit log, select Export, then confirm. Atlassian's page notes three details:
- The export is a CSV of up to 100,000 events. With more than that, the newest events are included.
- The export ignores your filter. All events up to the maximum are exported even if you filtered the page.
- The audit log is also available through the Jira Cloud REST API, which suits a scripted export.
The organization log exports differently. You select Export log, and Atlassian emails a CSV of up to 10,000 activities from the past 180 days. In this export your search and filters do apply. The download link expires a day later, so save the file when the email arrives.
A review routine that actually happens #
Reading the audit log only after something breaks makes it a forensic tool. Compliance frameworks expect more than that: a periodic review of privileged changes, with evidence that it took place. Our guides on Jira SOX compliance, Jira ISO 27001 and the Atlassian SOC 2 report all come back to the same point: the review is a control, and a missed period is a control failure.
A workable routine has three cadences.
| Review | What to look at | Example cadence |
|---|---|---|
| Permission and admin changes | Permission schemes, global permissions, group and role membership | Monthly |
| Workflow and field changes | Published workflows, required fields, screen changes on key projects | Monthly |
| Export and archive | A CSV of the period, saved where your evidence lives | Monthly, before retention runs out |
| Deleted work items | "Work item deleted" events and who made them | Quarterly |
| Retention setting check | The retention period is still what your policy says | Yearly |
Pick the cadence from your retention, not the other way round. With a 6-month retention, a quarterly export leaves room for one missed period. A yearly export does not.
What a good review ticket holds #
- a title naming the period, such as "Audit log review 2026-10";
- an owner and a due date, set when the ticket is created;
- the exported CSV attached, or a link to where it is stored;
- a short note of anything unexpected and what was done about it.
That ticket is the evidence. When the review lives only in someone's calendar, there is nothing to show for the month they were away.
Three ways to raise the review ticket #
| By hand | Jira Automation scheduled rule | Recurring Work Items for Jira | |
|---|---|---|---|
| Effort | Every ticket, every period | One rule, written once | One rule, chosen from a form |
| Schedule | Whoever remembers | Fixed rate or cron expression | Daily, weekly, or monthly on a day or a weekday, every N months |
| Lives in | Somebody's calendar | The automation rules list | The project that holds the reviews |
| Evidence a run happened | The ticket, if it was made | The rule's own log | Run history: created, skipped or failed, with the reason |
By hand #
Fine for one administrator who never misses the first Monday of the month. Cloning last month's ticket keeps the description consistent, and our Jira task template guide shows how.
Jira Automation #
A scheduled rule can create the review ticket on a fixed rate or a cron expression. "The first working day of the month" is awkward to say in cron, which our Jira cron expression guide explains, and scheduled runs count toward your automation usage, covered in Jira Automation pricing. Rule changes are themselves configuration worth reviewing, since a rule anyone can edit is a reminder anyone can switch off.
A scheduling app #
Recurring Work Items for Jira creates issues on a schedule, with rules scoped to one project. A project administrator turns it on for the security or admin project alone, and each rule keeps a run history showing whether the ticket was created, skipped or failed, and why.
Set up the audit log review calendar #
With Recurring Work Items, the setup is short:
- Choose the project that holds admin and security work, or create one.
- Turn the app on for that project only.
- Create one rule per review. A monthly review is a monthly rule; the yearly retention check is a monthly rule repeating every 12 months.
- Pick the day, such as "the first Monday of the month", so the spacing stays even.
- Set working days and holidays, then choose Move it to the next working day under If it falls on a non-working day, so a review never lands on a weekend: a new rule runs on the day it falls on, holiday or not.
- Title each period with tokens, for example
Audit log review {{now.year}}-{{now.month}}, so each month maps to one ticket. - Fill in the template: the owner, a due date a few days after the run, a label such as
audit-log-review, and a description listing the categories to check. - Add subtasks: export CSV, review permission changes, review workflow changes, note findings, attach evidence.
When an auditor asks for evidence, a filter on the label answers it in one query. If you run broader housekeeping too, our Jira hygiene guide fits alongside.
When the manual way is enough #
A scheduled review earns its place once more than one person administers the site, or once an auditor will ask about it. You may not need one if:
- you are on the Free plan, where the Jira audit log isn't available anyway;
- a SIEM already ingests the log, through the REST API or the organization log's webhooks, and alerts on the events you care about;
- a single administrator makes every change, and nobody outside the team asks for evidence.
FAQ #
Where is the audit log in Jira Cloud? Select Settings, then System, then Audit Log. You need the Administer Jira global permission.
Does the Jira audit log show who edited a ticket? No. Field edits and comments are in each work item's history. The audit log covers configuration changes and work item deletions.
Can I see who deleted a work item? Yes. Search the audit log for "work item deleted" or the item's key to see who deleted it and when.
How far back does the Jira audit log go? As far as your retention setting allows. You choose the period under Actions, then Audit Log Settings. Export regularly if you need a longer record.
Can Jira remind me to review the audit log? Not by itself. A scheduled rule, in Jira Automation or an app like Recurring Work Items for Jira, can create the review ticket each month with the owner and due date already set.