Jira Audit Log vs Issue History: What's the Difference?

Jira's audit log tracks configuration and permission changes across your whole site. Issue history tracks field-level changes on a single work item. So, they are not answering the same questions.

Before diving in, a quick note on terms: Jira Cloud now calls “issues” “work items”. We will use both in this post.

Here is a breakdown of what the audit log and issue history are, when to use them, and how to report on history when you need to look across many items at once.

What Does the Jira Audit Log Track?

The Jira audit log records configuration and administrative changes across your site. It answers one question: who changed the system, and when?

You can find it under Settings > System > Audit Log. You need the Administer Jira global permission to view it.

The audit log captures events like:

• Workflow changes (workflow created, copied, removed, renamed, or published, and statuses created or updated)
• Permission changes (permission schemes created or edited, global permissions granted or removed)
• Custom field changes (field created, updated, trashed, restored, or deleted)
• Screen and field configuration changes
• Work type and scheme changes
• Notification scheme changes
• Sprint changes (created, started, updated, closed, or deleted)
• Project changes (created, removed, or updated)
• User, group, and role changes
• Work item deletions, tracked by work item key, so you can see who deleted an item and when

There is one more gap. Jira does not currently let installed apps record their own configuration changes in the audit log, so if you change an app's settings, that change will not appear there. Atlassian is tracking this as an open request.

As seen in the list above, the audit log does not record the routine field changes inside a work item. A status moving from To Do to In Progress, an assignee change, a priority bump, or an edited description: none of that is in the audit log.

The one work-item event the audit log does keep is deletion. If a work item is deleted, the log shows who deleted it and when, searchable by work item key.

A few practical limits for admins:

• You cannot sort the log in the interface. You export to CSV and sort in a spreadsheet.
• Retention is configurable, for example 6 months, so older configuration events age out.
• Events from before the August 2024 audit log update may not appear.
• A known issue means the Author field may not show the username for some user management changes.
• The audit log is not available if all of your Jira apps are on the Free plan.

One more thing worth knowing: this post covers the Jira product audit log under Settings > System, which is where your Jira site's configuration changes are recorded and which any Jira admin can open.

What Does Issue History Track?

Issue history records field-level changes on a single work item. It answers a different question: what changed on this item, and who changed it? Open any work item, scroll to the Activity section, and select History. Atlassian describes this view as updates on a work item, such as when someone edits a field or moves the item through its workflow. See the different types of activity on a work item for the current definition. The data comes from the work item's changelog. Issue history shows changes like:

• Status transitions (To Do, to In Progress, to Done)
• Assignee changes
• Priority, summary, and description edits
• Custom field, label, and component changes
• Sprint and fix version changes

Anyone who can view the work item can see its history. No admin permission is needed, unlike the audit log.

Jira’s Native History Limitations

But native issue history has real limits. The first and probably most important one is that you can see one item at a time. You cannot see field changes across a group of items in one view.

Another problem is export. There is no export button on the History tab. Also, sorting is really basic. You can flip between newest and oldest, and that is about it.

For a single ticket, that is fine. For a sprint's worth of tickets, or a compliance review across a project, it falls short.

So a whole class of everyday questions has no native answer:

• Which tickets had their story points changed after the sprint started, and by whom?
• How did priority change across every bug last month?
• Who moved these five items back to In Progress, and when?
• What did the backlog look like on the day we released?

To answer these, you need to pull changelog data across many work items into one place, then filter, group, and export it. Jira does not do that on its own.

How to Report on Issue History Across Many Work Items

To report on field changes across many work items at once, you need a tool built on Jira's changelog. Historian - History Explorer for Jira does exactly that. Historian turns the raw changelog into a report you can work with:

Work Item History Report

Enter a JQL query, pick the fields you care about, and see the full history for every matching item in one table. Switch between a Work Item view, where all changes are grouped under each item, and a Field view, where each change is its own row. The Field-based View is best for tracking a single field across many items.

Filter, Group, and Sort

Narrow the report by date range, by the user who made the change, or by specific field values. Highlight changes with color to spot them fast.

Audit-ready Export

Download the filtered report to XLSX or CSV for audits, archiving, or stakeholder reviews. Admins can limit export to specific groups.

Compare Dates

Compare Dates is a separate screen. Pick one work item and two points in time, and Historian shows both states side by side so you can confirm exactly what changed between them.

Historic Query

It is another screen of its own. It rebuilds a JQL search as it stood on a past date, which gives you a clean backlog snapshot for audit time.

Historian AI Assistant

Instead of spending time figuring out JQL queries or complex filter settings, simply describe what you are looking for in plain English like, ‘who changed the status of PROJ-101 last week’. Powered by Atlassian Rovo, the AI Assistant analyzes your request and guides you step-by-step to configure the exact history report you need.

Historian respects Jira's permissions, so users only see history for items they already have permission to view. Try Historian for free on the Atlassian Marketplace, or book a live demo.