This page is about Time to SLA for Jira Cloud.
On this page, you can see all the operations performed in Time to SLA. All activity across Time to SLA will appear on this page, from the creation of an SLA to the editing of a single configuration.
Assume an important SLA was deleted and you don’t know who did it. Thanks to Audit Logs, you can learn who or what was behind it in an instant.
Let’s explore the Audit Logs page together:
Date – This is the date and time when the change was made.
Author – Displays who made the change. If you click the name, it takes you to the author’s profile.
Object type – Shows where the change was made. It can be SLA Configuration, Notifiers, Calendars, Permissions, Settings, Reports, and API Tokens.
ID – This is the ID of the changed object. For example, you can read the image below as: A Calendar with the ID 8ecdcfb9-6c1a-4a4d-8877-20c7231b2464 has been updated by Derya Özdemir on 18.08 2022, 12:35 pm.
Event type – Shows the status of the event. It can be Created, Updated, and Deleted.
Object data – Allows you to see the object data of the event.
Reload – Click to refresh your audit logs.
Reset search – Allows you to navigate to page 1 with one click.
Except for the Clean Old Audit Logs option, which we will explore later, no user can delete items in Audit Logs, which means all activity across the app is meticulously documented.
🚀 Next Steps
Now that we’ve taken a look at the Audit Logs page, we can go into further details such as using object data and deleting audit logs periodically.