Issue Summary

Events that are generated by user activity/action within Jira, should have associated user id stored alongside the event that is stored as a part of Jira audit log. Unfortunately for some events, author field is still missing.

Steps to Reproduce

There is no easy way to reproduce this issue at present. We just observe that for some events triggered by user activity, author filed is not populated.

Expected Results

Every event stored to Audit log database should have have reporter field set (if the event was triggered by Jira user). There is generic mechanism that reads the context of current user before event is stored within audit log table

Actual Results

Seems that for some customers, events that are generated (triggered) by the Jira user are stored in Audit log table without author field assigned. Please take look at the attachment.

Workaround

NA