A consultant who supports Jira customers recently told me which auditor question his clients bring to him again and again: who changed what, when, and who approved it, usually for a specific set of work items over a specific period. The data is in the work item history, he said, and the painful part is turning it into something an auditor can actually read.
Here is what Jira records natively for that question, and what admins can set up before the next audit.
Three kinds of evidence
The question sounds like one request, but it touches three different kinds of audit evidence. Work item history shows how individual items changed. Audit logs help track administrative and configuration activities. Approval evidence depends on the workflow and the controls around it. That is why no single Jira feature answers all of it.
What Jira already records
Jira records changes to supported work item fields in the activity history, including who made the change and when. For a single work item, this covers most of the change history. Whether a change was approved, and by whom, depends on how the approval process was implemented and documented.
Across many work items, JQL offers history operators such as WAS and CHANGED. The JQL field reference lists which operators each field supports, and the history operators are not available on every field. A query like status CHANGED DURING ("2026/01/01", "2026/03/31") returns the work items whose status changed in that period, as a list. The individual changes still have to be opened one by one.
The Jira audit log under Settings, System, Audit log is intended to record configuration changes that can impact users and spaces, and it is not intended to record all activity in Jira. It is not available if all Jira apps on a site are on the Free plan, and admins choose how long its entries are kept.
The organization audit log in Atlassian Administration requires an Atlassian Guard subscription (Standard or Premium) or at least one Enterprise plan. Without one, organization level logs do not store or display any events. Atlassian keeps these activities for up to one year.
For approvals, Jira Service Management lets admins add an approval step to a workflow status, so specific people must approve a work item before it moves on.
An example request
Imagine an auditor asks: show me all high priority work items that were moved to Done between January and March, who changed their status, and whether the required approvals were obtained.
JQL helps identify the relevant work items. The history of each work item shows who changed the status and when. Whether the required approvals were in place has to be checked against the documented approvals. Finding the data and providing audit evidence are two different tasks.
Where the effort comes from
The auditor asks about a set of work items and a period of time. The history view answers one work item at a time, JQL answers with a list, and the audit log covers configuration. Someone has to bring these together, usually the Jira admin, through exports, spreadsheets or the REST API.
Approvals are the hardest part. When an approval happens by email, chat or in a meeting, that evidence may exist outside Jira. The challenge is linking it reliably to the work item and making it available when an auditor asks.
Four steps before the next audit
Make approvals happen inside Jira. In Jira Service Management, use an approval step on the relevant workflow status. Atlassian also documents approval steps for other Jira spaces, with availability depending on space type and plan. Where native approval steps are unavailable, a restricted workflow transition can provide evidence of who performed the approval related action. However, the organization must define and document what that transition means and how authorization is controlled.
Protect the history you already have. According to Atlassian, a deleted work item is permanently removed from your site. On Premium and Enterprise plans you can archive a work item instead: it leaves the space without being deleted, can no longer be edited and can be restored later. Limit the permission to delete work items to a small group, check the retention setting of the audit log, and give integrations their own accounts so their changes are not recorded under a colleague's name.
Agree on scope and format with the auditor. Ask early which work items are in scope, which period counts, which fields matter as a change, and in what form the evidence should be delivered, for example an export, screenshots or a report.
Choose tooling by how often the question comes back. Once a year for a handful of work items, JQL and an export can be enough. If it comes back with every audit, across many spaces or clients, Marketplace apps can help collect relevant events, analyze changes across work items and spaces, and present the results in a format auditors can review. Check which events are covered, when recording begins, and whether historical data is available.
Recording is not the same as proving
A history shows what happened. Whether the intended controls were followed has to be traceable as well, and that part is set up before the audit, not during it.
How do your teams answer the "who approved it" part today, and where does that evidence live?
My own view, I'm not an Atlassian employee.