• Icon: Suggestion Suggestion
    • Resolution: Deployed
    • None
    • None
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

       

      Atlassian Update – 3 May 2019

      Hi everyone,

      I have good news! My team and I have released a new and improved audit log that contains many of the activities mentioned on this ticket. The log currently covers the following activities: 

      • A user was added to a group
      • A group was created / deleted
      • A group’s permissions were altered
      • And many more

      This new log works across your entire organization, aggregating events from all of your Jira and Confluence sites into one place. Although it only contains user and group management activities today, we are working on expanding the set of events on an ongoing basis.

      To use the log, you must have a valid Atlassian Access subscription or trial. The log can be accessed from: Organization administration settings -> Security -> Audit log (Beta). Please be aware that this is a beta version of the feature and you may encounter bugs. If this happens, please file a support ticket or comment on this issue so that we can continue to improve this feature.

      Thanks for voting and commenting on this issue. Your feedback has been incredibly helpful to our team as we’ve worked on bringing this information to you. We know how important audit logs can be to any organization, and sincerely apologize for any inconvenience this may have caused you.

      We remain focused on bringing more activities to the audit log and would love to hear any feedback you have for us. Please feel free to email me directly at rgarg@atlassian.com if needed.

      Thanks,
      Rak Garg
      rgarg@atlassian.com
      Product Manager, Atlassian

       
      Have advanced audit features in User management where a site admin can view audit of user who

      • added new users
      • created new groups
      • assigned users to groups
      • revoked a user 
      • deleted a user
      • deleted a Group

            [ACCESS-577] Audit log for user management

            Hi kevin.lau1,

            There shouldn't any performance impact to using the beta. The new audit log shows events across all of your Jira and Confluence sites in a single place, which is why you need to register an organization to use with your Jira site. Organizations associate multiple different products (like Jira, Confluence, etc) with a single customer. Additionally, you will need a subscription to Atlassian Access to use the new audit log. Please find more details on the documentation page for audit logs. .

            I hope this helps - let me know if you have any other questions.

            Rak Garg
            Product Manager, Atlassian Access

            Rak Garg (Inactive) added a comment - Hi kevin.lau1 , There shouldn't any performance impact to using the beta. The new audit log shows events across all of your Jira and Confluence sites in a single place, which is why you need to register an organization to use with your Jira site. Organizations associate multiple different products (like Jira, Confluence, etc) with a single customer. Additionally, you will need a subscription to Atlassian Access to use the new audit log. Please find more details on the documentation page for audit logs.  . I hope this helps - let me know if you have any other questions. Rak Garg Product Manager, Atlassian Access

            hi

            Chih-Wei Yang added a comment - hi

            Kevin Lau added a comment -

            Hi @Rak Garg,

            I am an administrator of my companies site.  Before we use the Beta what is the implications e.g. performance impact or notifications etc of following the steps attached? Is there a reason why I need to register my organisation to use Jira?  Once I have finished using the Beta how do I unregister and will this break anything?  

             

            Thanks

            Kevin

            Kevin Lau added a comment - Hi @Rak Garg, I am an administrator of my companies site.  Before we use the Beta what is the implications e.g. performance impact or notifications etc of following the steps attached? Is there a reason why I need to register my organisation to use Jira?  Once I have finished using the Beta how do I unregister and will this break anything?     Thanks Kevin

            Hi kenzy.clerdonna

            Thanks for your feedback. I totally understand that it's a major inconvenience to not have access to this information. Fortunately, we have rolled out a new and improved audit log to all Atlassian Access customers that contains the majority of user and group management actions that have been mentioned on this ticket. The new log can be accessed from: Organization administration settings -> Security -> Audit log (Beta). Please feel free to email me at rgarg@atlassian.com if you have any questions or suggestions. 

            Cheers, 

            Rak Garg

            Product Manager, Atlassian 

             

            Rak Garg (Inactive) added a comment - Hi kenzy.clerdonna ,  Thanks for your feedback. I totally understand that it's a major inconvenience to not have access to this information. Fortunately, we have rolled out a new and improved audit log to all Atlassian Access customers that contains the majority of user and group management actions that have been mentioned on this ticket. The new log can be accessed from:  Organization administration settings -> Security -> Audit log (Beta).  Please feel free to email me at rgarg@atlassian.com  if you have any questions or suggestions.  Cheers,  Rak Garg Product Manager, Atlassian   

            Is there a way to specify the Jira administrator who creates a user, adds users to groups, etc? It would be a strenuous process contacting support to retrieve the specific name of the author everytime.

            Kenzy Clerdonna added a comment - Is there a way to specify the Jira administrator who creates a user, adds users to groups, etc? It would be a strenuous process contacting support to retrieve the specific name of the author everytime.

            Peter Fjelsten added a comment - - edited

            So basic auditing is available only to those who pay even more to Atlassian?

             

            Shame on you. This should be in the default package!

            Peter Fjelsten added a comment - - edited So basic auditing is available only to those who pay even more to Atlassian?   Shame on you. This should be in the default package!

            Atlassian Update – 3 May 2019

            Hi everyone,

            I have good news! My team and I have released a new and improved audit log that contains many of the activities mentioned on this ticket. The log currently covers the following activities: 

            • A user was added to a group
            • A group was created / deleted
            • A group’s permissions were altered
            • And many more

            This new log works across your entire organization, aggregating events from all of your Jira and Confluence sites into one place. Although it only contains user and group management activities today, we are working on expanding the set of events on an ongoing basis.

            To use the log, you must have a valid Atlassian Access subscription or trial. The log can be accessed from: Organization administration settings -> Security -> Audit log (Beta). Please be aware that this is a beta version of the feature and you may encounter bugs. If this happens, please file a support ticket or comment on this issue so that we can continue to improve this feature.

            Thanks for voting and commenting on this issue. Your feedback has been incredibly helpful to our team as we’ve worked on bringing this information to you. We know how important audit logs can be to any organization, and sincerely apologize for any inconvenience this may have caused you.

            We remain focused on bringing more activities to the audit log and would love to hear any feedback you have for us. Please feel free to email me directly at rgarg@atlassian.com if needed.

            Thanks,
            Rak Garg
            rgarg@atlassian.com
            Product Manager, Atlassian

            Rak Garg (Inactive) added a comment - Atlassian Update – 3 May 2019 Hi everyone, I have good news! My team and I have released a new and improved audit log that contains many of the activities mentioned on this ticket. The log currently covers the following activities:  A user was added to a group A group was created / deleted A group’s permissions were altered And many more This new log works across your entire organization, aggregating events from all of your Jira and Confluence sites into one place. Although it only contains user and group management activities today, we are working on expanding the set of events on an ongoing basis. To use the log, you must have a valid Atlassian Access subscription or trial. The log can be accessed from: Organization administration settings -> Security -> Audit log (Beta). Please be aware that this is a beta version of the feature and you may encounter bugs. If this happens, please file a support ticket or comment on this issue so that we can continue to improve this feature. Thanks for voting and commenting on this issue. Your feedback has been incredibly helpful to our team as we’ve worked on bringing this information to you. We know how important audit logs can be to any organization, and sincerely apologize for any inconvenience this may have caused you. We remain focused on bringing more activities to the audit log and would love to hear any feedback you have for us. Please feel free to email me directly at rgarg@atlassian.com if needed. Thanks, Rak Garg rgarg@atlassian.com Product Manager, Atlassian

            Please track when a user is removed from a group.

            Leslie Devlin added a comment - Please track when a user is removed from a group.

            Audit log is not audit log without this informations

            Balazs Varga added a comment - Audit log is not audit log without this informations

            Hi Team,

             

            This is very important for us when we try to track a specific event where a user was added to an Atlassian group by a Site admin the audit log does not give relevant information - the end user who was responsible for this action.

            Cheers

            Ankit

            Ankit Arora added a comment - Hi Team,   This is very important for us when we try to track a specific event where a user was added to an Atlassian group by a Site admin the audit log does not give relevant information - the end user who was responsible for this action. Cheers Ankit

            Hi All,

            We would also like to see as mentioned also by @Gary May

            • Authentication/Access logs
            • System configuration change events
            • System/security events

            This is a standard Enterprise need and is required by our SIEM team to proactively monitor usage.

            Cheers

            Lee

            Lee Dennison added a comment - Hi All, We would also like to see as mentioned also by @Gary May Authentication/Access logs System configuration change events System/security events This is a standard Enterprise need and is required by our SIEM team to proactively monitor usage. Cheers Lee

             

            Atlassian Update – 15 November 2018

            Hi everyone,

            Thanks for voting and commenting on this issue. We would love to learn more about how you use audit logs. We appreciate if you could please fill out our short survey here.

            Your feedback is key to helping us understand how we can continue improving your experience with our products. 

            Thanks,
            Rak Garg
            Product Manager, Atlassian

             

            Rak Garg (Inactive) added a comment -   Atlassian Update – 15 November 2018 Hi everyone, Thanks for voting and commenting on this issue. We would love to learn more about how you use audit logs. We appreciate if you could please fill out our short survey here. Your feedback is key to helping us understand how we can continue improving your experience with our products.  Thanks, Rak Garg Product Manager, Atlassian  

            Atlassian Update – 14 September 2018

            Hi everyone,

            Thanks for voting and commenting on this issue. Your feedback is key to helping us understand how we can continue improving your experience with our products.

            This feature is currently on our roadmap. In the meantime, please watch this ticket for further updates.

            Regards,
            Rak Garg
            Product Manager, Atlassian

            Rak Garg (Inactive) added a comment - Atlassian Update – 14 September 2018 Hi everyone, Thanks for voting and commenting on this issue. Your feedback is key to helping us understand how we can continue improving your experience with our products. This feature is currently on our roadmap. In the meantime, please watch this ticket for further updates. Regards, Rak Garg Product Manager, Atlassian

            Leaving a note here to feature requests to :

            Log sync data happened when using Gsuite to sync your user base and make that data available for administrators to download and review:

            *https://jira.atlassian.com/browse/ID-6548*

            Rate limiting changes in the case of many changes happening in 1 automated sync, ie if someone disables or make mass changes accidentally that it shouldn't result in a massive overhaul in your atlassian instance:

            *https://jira.atlassian.com/browse/ID-6549*

             

            Carel Starreveld added a comment - Leaving a note here to feature requests to : Log sync data happened when using Gsuite to sync your user base and make that data available for administrators to download and review: * https://jira.atlassian.com/browse/ID-6548* Rate limiting changes in the case of many changes happening in 1 automated sync, ie if someone disables or make mass changes accidentally that it shouldn't result in a massive overhaul in your atlassian instance: * https://jira.atlassian.com/browse/ID-6549*  

            Garry May added a comment -

            How about:

            1. Modifications to User Account details, for example, deactivation (when, what properties etc?)
            2. User logins (success/failures, when, IP address etc)
            3. If the user is an Admin, who, when and how long (date/time) they impersonated another user 

            Garry May added a comment - How about: Modifications to User Account details, for example, deactivation (when, what properties etc?) User logins (success/failures, when, IP address etc) If the user is an Admin, who, when and how long (date/time) they impersonated another user 

            Is this for JIRA Cloud?

            Taulbee Davis added a comment - Is this for JIRA Cloud?

              Unassigned Unassigned
              asridhara Adarsh
              Votes:
              69 Vote for this issue
              Watchers:
              86 Start watching this issue

                Created:
                Updated:
                Resolved: