![]() You may use this to:Īdd events to the audit log triggered by external pluginsįor more information on using the REST API, check out the Jira Cloud REST API documentation. The audit log can also be accessed via the REST API. Navigate to the audit log and choose Export When you export the audit log, all events (up to the maximum number) are included even if you've filtered the audit log results in the page. If you have more than 100,000 events, the newest events are included in the export. Changes to computer software must be monitored in order to reduce the risk of data loss, corruption, malware, errors, and security breaches. You can export up to 100,000 events as a CSV file. Change management auditing is the process by which companies can effectively manage change within their information technology systems. Update the retention period and external user directory settings and choose Save Adjustments may be required to materiality, scoping and sampling strategies. ![]() For example, systems should be assessed and tested to ensure they can accommodate procedures within a shortened transition period. You can configure how long audit events are retained, and whether events from external user directories like LDAP appear in the log. Changes to systems and technology, as well as the downstream impact to internal controls and internal audit functions. For example, events like users being created or assigned to groups won't include the username of the user who made the change. There's a known issue which prevents the Author field from displaying the username for changes that were made in the user management pages in Jira cloud products (including changes to users, groups, and application access). ![]() You can export the data to a CSV file and open it in a spreadsheet application to manipulate the data. The audit log is intended to record configuration changes that can impact users and projects. For example, it doesn't track issue updates or pages that are viewed by a user. The audit log isn't intended to record all activity in Jira. Plan created, plan deleted, plan updated (includes scheduling configurations, adding or removing issue sources, and changing of exclusion rules), and when permissions in Advanced Roadmaps change Scheme created, scheme copied, scheme removed, scheme edited, scheme added to project, scheme removed from project, notification added to scheme, notification removed from scheme.Ĭustom field created, custom field updated, scheme added to project, scheme removed from project, custom field trashed, custom field restored, custom field deleted Scheme created, scheme copied, scheme removed, scheme edited, scheme assigned to a project, scheme unassigned from a project, workflow created, workflow copied, workflow removed, workflow renamed, workflow draft published Scheme created, scheme copied, scheme removed, scheme edited, scheme assigned to a project, scheme unassigned from a project, permission added to scheme, permission removed from scheme, global permission added to a group, global permission removed from a group Project created, project removed, project updated
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |