We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-37378

Audit log does not allow to hide non-human changes

XMLWordPrintable

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

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

      We have a user directory with 17.000 users and obviously the number of changes made on directory sync (Crowd) is quite relevant.

      This is spamming the audit log making it impossible to be used for identification of changes made by humans (these were made by "JIRA" itself).

      It seems that the workaround would be to enable a minimal level of filtering for the audit log browser.

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Jira Data Center'
            1. Jira Data Center
            2. JRASERVER-37378

            Audit log does not allow to hide non-human changes

            XMLWordPrintable

              • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

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

                We have a user directory with 17.000 users and obviously the number of changes made on directory sync (Crowd) is quite relevant.

                This is spamming the audit log making it impossible to be used for identification of changes made by humans (these were made by "JIRA" itself).

                It seems that the workaround would be to enable a minimal level of filtering for the audit log browser.

                        Unassigned Unassigned
                        intersol_old intersol_old
                        Votes:
                        1 Vote for this issue
                        Watchers:
                        4 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Unassigned Unassigned
                            intersol_old intersol_old
                            Votes:
                            1 Vote for this issue
                            Watchers:
                            4 Start watching this issue

                              Created:
                              Updated:
                              Resolved: