In Jira Cloud site's audit log, with system-relevant entries the Author is displayed simply as JIRA. Examples include project role changes (see attached screenshot) or events such as creating or deleting a group.

However, when checking the Organization audit log, we can confirm that many of these actions were actually performed by a specific user (e.g., a Site-Admin or Product-Admin) through the administrator interface.

Because some customer might have policies which separates organization-level administration from site administration, the site-admin team does not have access to the organization audit log.

This creates a compliance and traceability gap for ISO 27001 and internal auditing, since we cannot identify which individual performed the action.

Impact:

• Lack of user attribution complicates security investigations and ISO 27001 audits.
• Site-admins must repeatedly escalate to the org-admin team for basic change history, which is inefficient.

Expected Results:

• There should be a configuration option that allows the Jira Cloud audit log to resolve the "JIRA" author into the actual initiating user?
• If not configurable, can Atlassian enable or adjust our instance so that the audit log records the real user who initiated the change (site-admin or product-admin) rather than the generic "JIRA" system account?
• If neither is currently possible, can you provide a recommended workaround or roadmap for improving this logging behaviour?