Hi Atlassian Community,
I noticed mismatch in jira:
1) The issue history shows a field was updated by a person with exact date and time.
2) But there is no corresponding entry in the Audit Log.
The person was saying that they just viewed not modified it,
could anyone help me understand why this inconsistency occurs and how to verify what actually happened?
Hi Usha 👋
That’s a good question — it’s common to see differences between issue history and the audit log.
In short:
Issue history tracks field-level changes.
Audit log focuses on admin-level actions.
If a change was made by automation, a bulk edit, or a system process, it might show in the issue history but not the audit log.
For a clear breakdown of how Jira tracks changes and what each log includes, this post explains it well:
Auditing in Jira: How to Track User and System Changes
Hope it helps! 😊
Hello @Usha Rani Pala
Welcome to the Atlassian community.
The system Audit Log does not record every change in every field for every issue. For details about what it does include, refer to
https://support.atlassian.com/jira-cloud-administration/docs/audit-activities-in-jira-applications/
The individual issue's History is the "Audit Log" for changes to fields for that issue.
If the user did not make the change you could investigate if they caused an Automation Rule to run which made the change on their behalf.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Trudy Claspill,
The field update is visible in the issue history, but there is no corresponding entry in audit log. considering the scope of the issue is significant, (I've checked and don't have automation rule to run on this) how can this be investigated further?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I've already explained why there is no entry in the System Audit Log.
You could open a support request directly with Atlassian for additional help investigating the issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.