Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-7846

Enterprise level auditing

XMLWordPrintable

    • 6
    • 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.

      This is a feature entry to guage the interest in Atlassian providing an enterprise level auditer.

      An enterprise level auditer would be distinguishable from currently available logging services for the following reasons:

      • Logging information is accessible via the Administration UI.
      • Logging info. can be persisted in a database table if needed.
      • Logging priorities are configurable on a component by component basis - i.e. an admin. could choose to audit security at a detailed level but only receive general notices about content creation. This configuration would occur in the Administration UI.

      Another possible point to consider is logging across a cluster. If it ever appears the auditer might be leveraged to let admin.s administer federated logging.

      NOTE - the clustering comment applies to current thinking for Confluence, not JIRA.

      Furthermore, it would be nice if the auditer could work across both Confluence and JIRA - both product customers probably have a need for this level of logging. I'm creating this issue under Confluence for the timebeing but it is a relevant consideration for JIRA also.

            Unassigned Unassigned
            nick@atlassian.com Nick Faiz [OLD] (Inactive)
            Votes:
            40 Vote for this issue
            Watchers:
            26 Start watching this issue

              Created:
              Updated:
              Resolved: