NOTE: This suggestion is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? See the corresponding suggestion.
Hi all,
We are very excited to let you know that this issue has been fixed! We've added the Jira Service Management configurations to the audit logs
You may find more details at Track organization activities from the audit log
Problem definition
Changes in the Service Desk configuration does not log an entry into the audit logs causing admins to not know who and what changes were done.
- Customers added/Removed to a JSM Project.
- Organizations added/Removed to a JSM project.
- JSM Global configuration update
Suggested solution
Include the changes into audit logs by recording who and what is changed
Why is it important
The information would allow more transparency towards the changes in configuration.
- is related to
-
JRACLOUD-79986 [Tracking in Issue Links] Site-level audit log feature requests
- Gathering Interest
- relates to
-
- Gathering Interest
- mentioned in
-
Page Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[ACCESS-1350] Include Jira Service Management (Service Desk) configuration changes to audit logs
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
| Description |
Original:
h3. Problem definition
Changes in the Service Desk configuration does not log an entry into the audit logs causing admins to not know who and what changes were done. * Customers added/Removed to a JSM Project. * Organizations added/Removed to a JSM project. * JSM Global configuration update h3. Suggested solution Include the changes into audit logs by recording who and what is changed h3. Why is it important The information would allow more transparency towards the changes in configuration. |
New:
{panel:bgColor=#e7f4fa}
*NOTE:* This suggestion is for {*}JIRA Service Desk Cloud{*}. Using {*}JIRA Service Desk Server{*}? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSDSERVER-1211]. {panel} {panel:title=Updated 5 February 2024} Hi all, We are very excited to let you know that this issue has been fixed! We've added the Jira Service Management configurations to the audit logs You may find more details at [Track organization activities from the audit log|https://support.atlassian.com/security-and-access-policies/docs/track-organization-activities-from-the-audit-log/] {panel} h3. Problem definition Changes in the Service Desk configuration does not log an entry into the audit logs causing admins to not know who and what changes were done. * Customers added/Removed to a JSM Project. * Organizations added/Removed to a JSM project. * JSM Global configuration update h3. Suggested solution Include the changes into audit logs by recording who and what is changed h3. Why is it important The information would allow more transparency towards the changes in configuration. |
| Remote Link | New: This issue links to "Page (Confluence)" [ 846209 ] |
| Support reference count | Original: 7 | New: 8 |
| Support reference count | Original: 6 | New: 7 |
| Support reference count | Original: 5 | New: 6 |
| Link | New: This issue relates to ACCESS-1628 [ ACCESS-1628 ] |
| Support reference count | Original: 4 | New: 5 |
| Support reference count | Original: 3 | New: 4 |
| Support reference count | Original: 2 | New: 3 |