...
Audit logs for your team that manages operations help the IT administrators and Atlassian support teams troubleshoot integrations and issues related to configuration changes. Audit logs are accessible to only the admins (organization, site, or product, or team) and team members that are given additional permissions to view them). If you’re a team admin, contact the admin for your organization, site, or product for access permissions.
Audit logs is the best place to go to view all the incoming data related to your integrations and configuration updates or if you’re having trouble with your integrations for your team that’s managing operations.
...
The log category tells you whether the record relates to a notification, alert, integration, etc.
Jira Service Management System Actions: Captures information about system-originated actions (incoming data and automation).
Jira Service Management User Actions: Captures information about user-originated activity in the following areas. For example, configuration changes at a product or integration level, project settings, assets (global schemas, reference, status, icons), etc.
...
Jira Service Management User Actions: Captures information about user-originated activity in the following areas. This The following isn’t an exhaustive list, but it gives you an idea of what is covered.
Alerts
API
Integrations
Emails
Heartbeats
Incidents
Notifications
On-call schedulesUser management
An activity could be a create/change/delete action taken in relation to any of these entities.
| Expand | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||
|
Log levels
There are five three logging levels available in audit logs:
...
| Expand | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|
