Uploaded image for project: 'Atlassian Guard'
  1. Atlassian Guard
  2. ACCESS-1350

Include Jira Service Management (Service Desk) configuration changes to audit logs

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • Audit Log
    • 0
    • 8

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? See the corresponding suggestion.

      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

      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.

        1. 810-440-dumps.pdf
          407 kB
          Jake North
        2. CCSP dumps.pdf
          437 kB
          Peter Ross

            a620038e6229 Jehan Gonsalkorale
            nmohdkhalid Nabil
            Votes:
            19 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated:
              Resolved: