Jira audit log vs issue history — what's the difference?

When someone asks “who changed this in Jira?”, they get pointed at one of two different records — and the two get confused constantly. Knowing which is which (and what neither one does) saves a lot of digging.

The two native records

The admin audit log (Jira settings → System → Audit log) records site-level events: configuration changes, permission and role changes, user management, workflow and scheme edits. It’s an administrator’s record of “who changed the setup of Jira.”

Its limits for investigating actual work:

• It’s admin-only, and the full log isn’t available on the Free plan.
• Retention is bounded — older events age out, so a question about something from months ago may have no record.
• It’s not built for sorting/filtering an investigation, and it does not hold issue field values.

Issue history (the History tab on an issue) records field-level changes for that one issue: status transitions, assignee changes, field edits — who, when, and from → to.

Its limits:

• One issue at a time. There’s no way to ask “show me every priority change across these 40 issues.”
• No export. You can read it on screen, but you can’t pull it into a spreadsheet or an audit pack.
• It’s the native activity view, which leaves gaps — not every field change is surfaced as clearly as you’d want for a real audit.

The gap neither one fills

Put the two together and there’s an obvious hole: “show me who changed this field across these issues, over this period, and let me export it.” The admin log has the wrong scope (site config, not issue values); issue history has the right data but only one issue at a time and no export. For anything that looks like an audit — a compliance review, a “why did this estimate change” investigation, a dispute over who reassigned work — the native tools make you click issue by issue and transcribe.

Closing the gap

This cross-issue, exportable field-change history is exactly what an audit-trail app provides. Trailkeeper’s free tier gives a readable per-issue view; its paid tier adds the cross-issue, exportable record Jira’s native activity view leaves out — who changed what, when, and from which value to which.

Why that matters:

• Cross-issue, not one-at-a-time — answer “who changed X across this set of work” without opening each issue (paid tier).
• A durable record, since install — on the paid tier, history is captured to an independent store as it happens, so it’s there even after retention windows or deletions would have lost it — for issues tracked from install onward.
• Audit-ready — the who/what/when/old→new that reviews and disputes actually need, in one place.

Which do you use?

• Investigating a config or permission change? The admin audit log.
• Checking the change history of a single issue? The issue’s History tab.
• Need field-change history across many issues, or an exportable audit record? That’s an audit-trail app like Trailkeeper — the native tools stop exactly where that need starts. See who deleted an issue and the best Jira audit-log apps.