-
Suggestion
-
Resolution: Unresolved
-
59
-
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'.
- is duplicated by
-
MP-109 System apps are installed by anonymous user. Please update the name to System user
- Closed
- is related to
-
JRACLOUD-77967 Installing add-ons for Jira shows anonymous on the audit log instead of actual user
-
- Closed
-
-
JRACLOUD-79986 [Tracking in Issue Links] Site-level audit log feature requests
- Gathering Interest
- relates to
-
JRACLOUD-3157 JIRA Administration Audit trail / notifications
- Closed
-
MP-84 Include Add-ons changes information in Audit Log i.e. install / enable / disable apps in marketplace
- Gathering Interest
[MP-74] Show user responsible for action on Add-on Audit Log
Labels | New: jsw-s11 |
Remote Link | New: This issue links to "Page (Confluence)" [ 846043 ] |
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 ] |
UIS | Original: 58 | New: 59 |
UIS | Original: 59 | New: 58 |
UIS | Original: 52 | New: 59 |
Support reference count | Original: 84 | New: 85 |
UIS | Original: 46 | New: 52 |
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.