Skip to main content

Run an Audit

Audit 360 audits are read-only. Running an audit gathers supported signals, writes summarized results, and leaves Jira configuration unchanged.

Run a Custom Fields Audit​

  1. Open Audit 360 for Jira from Jira administration.
  2. Select Custom Fields Audit.
  3. Open Audit Overview.
  4. Select Run New Audit.
  5. Keep the page open while progress is displayed, or return later and load the completed run from the latest available result or Audit Library.

Custom Fields audits scan eligible unlocked custom fields. They do not require you to select fields manually.

Run a Spaces Audit​

  1. Open Audit 360 for Jira from Jira administration.
  2. Select Spaces Audit.
  3. Open Audit Overview.
  4. Select Run New Audit.
  5. Keep the page open while progress is displayed, or return later and load the completed run from the latest available result or Audit Library.

Spaces Audit reviews Jira spaces/projects, ownership signals, activity signals, configuration signals, and governance findings. It does not change Jira spaces/projects.

What Happens During the Audit​

Audit 360 reads supported Jira configuration and usage signals. For Custom Fields Audit, this includes field inventory, configuration references, dependency signals, associated spaces where available, and count-only population checks. For Spaces Audit, this includes Jira space/project inventory, count-only activity signals, feature configuration where available, and saved-filter, board, and dashboard dependency signals where metadata is available.

The audit stores summarized results so you can review the run later. It does not store raw Jira API payloads or individual work item keys in durable results.

When to Rerun​

Rerun an audit when Jira configuration has changed, when you need fresh evidence for a cleanup review, or before a high-impact administration change.