Uploaded image for project: 'Atlassian Guard'
  1. Atlassian Guard
  2. ACCESS-1146

Provide a comprehensive log of user activity

XMLWordPrintable

    • 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.

      Current audit logs in Jira, Confluence, and Atlassian Access primarily display administrator activity and some individual user actions (like logins). However, customers with extensive security or regulatory obligations require the ability to review individual user actions, like when certain issues or pages were viewed.

            [ACCESS-1146] Provide a comprehensive log of user activity

            Jonathon Yu added a comment -

            Hi all, we launched user activity logs within the audit log as part of Cloud Enterprise last quarter. While the new logs aren't completely comprehensive, they do cover widely-requested events around users viewing and interacting with Jira tickets and Confluence pages. You can find out more here: https://community.atlassian.com/t5/Enterprise-articles/Track-access-to-your-data-and-meet-compliance-needs-with-user/ba-p/1859518

            From here on out we'll be tracking additional logging needs and feature delivery in a more focused way (example: Bitbucket repository configuration logs). Comprehensive means different things to different types of orgs and users, so we want to keep the focus on specific logging capabilities and coverage.

            Jonathon Yu added a comment - Hi all, we launched user activity logs within the audit log as part of Cloud Enterprise last quarter. While the new logs aren't completely comprehensive, they do cover widely-requested events around users viewing and interacting with Jira tickets and Confluence pages. You can find out more here: https://community.atlassian.com/t5/Enterprise-articles/Track-access-to-your-data-and-meet-compliance-needs-with-user/ba-p/1859518 From here on out we'll be tracking additional logging needs and feature delivery in a more focused way (example: Bitbucket repository configuration logs). Comprehensive means different things to different types of orgs and users, so we want to keep the focus on specific logging capabilities and coverage.

              jyu@atlassian.com Jonathon Yu
              dmeyer Dave Meyer
              Votes:
              5 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: