Jira Audit Log vs. Issue History: What Each Tracks, and How to Report Across Work Items

[#1]

Audit logs and issue history in Jira record many types of changes and answer various inquiries. As each answers different kinds of questions, knowing the difference saves time. Knowing where both run out of road helps you determine whether a specialized reporting tool is worthwhile.
In Jira, audit logs and issue history (or work item history) record different kinds of changes and answer different questions. So, Jira audit log can’t tell you who edited a field on a work item. That's not what it tracks.
Knowing their capabilities and limitations saves you time, and knowing where both fall short tells you when you need a dedicated reporting tool.

Jira Audit Log Tracks System Changes

The audit log is a record of configuration and administrative activity across your Jira site. It answers the question of who changed the system and when. It is located under Settings > System > Audit Log, and opening it requires the Administer Jira global permission.

 

Its scope is site-wide, including workflow, permission, custom field, and screen changes, as well as project, user, group, role, and sprint activities. It excludes day-to-day field activity within a work item. Audit logs do not track changes in status from To Do to In Progress, priority changes, or updated descriptions.

What Jira Issue History Tracks

Issue history tracks field changes on a single work item, logging each field-level change. It answers the question of what changed on a work item and who was responsible. To access it, open a work item, navigate to the Activity section, and select History. No administrator permission is required; anyone who can see the work item can read its history. You can see status transitions, assignee changes, priority and description edits, custom field and label updates, sprint and version changes, and more. So, it is great to see all the changes to the issues. However, the challenge arises when you need to see multiple issues at once.

 

Where native issue history stops

History is limited to one item on screen at a time; there is no combined view of field changes across a set of items. The History tab has no export option, and sorting does little more than switch between newest and oldest first.

Here are some questions history tab cannot answer:

• After a sprint began, which items had their story points changed, and by whom?

• How did priority move across every bug in the last month?

• Who sent these issues back to In Progress, and when?

• What did the backlog look like on the day you shipped?

Each of these requires changelog data from many work items gathered in one place, then filtered, grouped, and exported. Jira does not offer that natively.

Reporting Across Many Work Items with Historian

Historian – History Explorer for Jira reads Jira's changelog and turns it into a report you can actually work with.

• Historian reads Jira's changelog and turns it into reports. It has three separate screens: The Work Item History Report is the main one. You enter a JQL query, pick the fields to track, and get the full history for every matching item in one table, with a Work Item view and a Field view. Filter by date, user, or field value, then group, sort, and export to XLSX or CSV.

• Compare Dates puts one item's state at two points in time side by side, so you can see exactly what changed between them.

• Historic Query rebuilds a JQL search as it stood on a past date, which gives you a clean backlog snapshot for audits.

• AI Assistant describe what you need in plain English. For example, you can ask "who changed the status of PROJ-101 last week" and it guides you to the report that answers it.

Historian enforces Jira permissions, ensuring users only see the history of issues they can access.

You can find Historian - History Explorer for Jira on the Atlassian Marketplace.