Hi @Reg Garg,

I beg to differ.  This ticket clearly states "For audit reasons customers would like to have an administration change log so they can track the people who made changes." This relates to JST-394792 which I raised with you in June 2018.

Hi nil dominic.wolfenden,

This ticket was never meant to track Jira-specific administration events – these are tracked separately in JRACLOUD-3157. The reason this ticket was created separately is that user management events for an Atlassian Cloud site apply to both Jira and Confluence and are distinct from Jira and Confluence administration activity. In the future, we will expand the scope of Atlassian Cloud administration audit logging to support our other products like Bitbucket Cloud and Trello.

@Rag Garg.

The above comment is correct.  Audit information relating to user management is not the same as audit infomration relating to "system" events that are in fact Admin events.  This should be reopened.

ACCESS-557 does not cover audition of issue state name changes. It has narrower scope than this one. Please REOPEN!

Six and a half years since this critical compliance related requirement was logged with your company that according to your own blurb has "Millions of users globally rely on Atlassian products every day".  When is this issue going to be assigned to one of your dev’s and fixed?  What is your ETA, why is your priority medium when there are clear compliance requirements for auditability here and how can you have tickets sitting unassigned for six and a half years unworked on? Are you providing enterprise solution or is this a student project with ambitions of grandeur?

this is pretty bad as there are valid use cases everywhere for this. Case in point: admins have a compliance reason and core need to see who made changes to user accounts. It's extremely sad (and i would imagine embarrassing for atlassian) that it has been over 5 years since this bug issue was first reported and paying customers still don't have a useable audit trail for cloud users. To be clear: we are failing a specific compliance requirements due to this.

We have a concern with how the Add-On Audit Log is updated. It shows that an "anonymous" ID makes changes to JIRA. There is no helpful description on the item as to what may have triggered the activity. Nor is a formal notification received stating there are changes that will be happening. We are requesting that a name & description be appended to these changes instead of "anonymous"?

This is a must have feature as far I am concerned. I should have log entries of changes being done especially de-activation and re-activation of users and user rights