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

      When accessing the Audit Logs for Add-ons, changes made by System are shown as made by anonymous user, as shown on picture below:

      This information should be more clear/specific, as for now showing anonymous is not helpful at all. To access these logs, go to JIRA Administration > Add-ons, navigate to Manage Add-ons and click Audit Logs.

      Additional information.

      When apps are installed by a user visiting the Mange-apps page on a Jira instance, then the user information is recorded correctly on the UI. However, when an app is installed from the backend by the system because a purchase order for the app was submitted or there was an app update or even a system app install, then the user information is not shown correctly on the UI and appears as 'anonymous'.

            [MP-74] Show user responsible for action on Add-on Audit Log

            Amir made changes -
            Labels New: jsw-s11

            Seeing who did what and when in the event history is essential for security audits and often valuable for day-to-day administration. Some events should be logged forever, like add-installations and resource creations. Who did what, when, and how exactly? Knowing, for example, how an add-on was installed (descriptor link, file upload, marketplace) is crucial to identify how to avoid getting charged for our own applications; for example, when you, let's say, as an admin, inherited a site from a former employee.

            Tempo Admin added a comment - Seeing who did what and when in the event history is essential for security audits and often valuable for day-to-day administration. Some events should be logged forever, like add-installations and resource creations. Who did what, when, and how exactly? Knowing, for example, how an add-on was installed (descriptor link, file upload, marketplace) is crucial to identify how to avoid getting charged for our own applications; for example, when you, let's say, as an admin, inherited a site from a former employee.
            Kat N made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 846043 ]

            Our Audit team are not happy with seeing Anonymous when looking at who has made changes. Doesn't help with our governance process. 

            Ian Mckenzie added a comment - Our Audit team are not happy with seeing Anonymous when looking at who has made changes. Doesn't help with our governance process. 
            pqz made changes -
            Component/s Original: Ecosystem - Marketplace [ 62392 ]
            Component/s New: DO NOT USE – placeholder for items assigned to previous component strucuture [ 73399 ]
            Key Original: JRACLOUD-67314 New: MP-74
            Support reference count Original: 85
            Project Original: Jira Cloud [ 18514 ] New: Atlassian Marketplace [ 22910 ]
            SET Analytics Bot made changes -
            UIS Original: 58 New: 59
            SET Analytics Bot made changes -
            UIS Original: 59 New: 58
            SET Analytics Bot made changes -
            UIS Original: 52 New: 59
            SET Analytics Bot made changes -
            Support reference count Original: 84 New: 85
            SET Analytics Bot made changes -
            UIS Original: 46 New: 52

              Unassigned Unassigned
              lhubert@atlassian.com Leonardo H
              Votes:
              66 Vote for this issue
              Watchers:
              88 Start watching this issue

                Created:
                Updated: