Skip to main content

Spaces Audit Details

Audit Details shows the normalized evidence behind a loaded Spaces Audit run. It is designed for reviewing one run at a time without changing Jira configuration.

What the Details Table Shows​

Audit Details includes:

  • Loaded run identity.
  • A paginated spaces table.
  • Inventory, activity, feature, filter impact, and risk signals.
  • Coverage notes for non-blocking warnings and partial access.
  • An inspect action for each row.

Export controls are not visible in the launch UI.

Inspect View​

Use the inspect action to review evidence for one space. The inspect view can include:

  • Execution details.
  • Space profile.
  • Governance and activity.
  • Feature configuration.
  • Direct filter impact.
  • Indirect board impact.
  • Indirect dashboard impact.
  • Governance findings.

The inspect view does not display raw Jira API payloads, work item keys, credentials, secrets, or tokens.

Coverage Notes and Partial Data​

Coverage notes explain non-blocking warnings and partial access. For example, board or dashboard dependency evidence can be incomplete when Jira APIs or permissions restrict visibility.

Partial coverage does not mean Audit 360 changed Jira. It means the audit result should be reviewed with that coverage limitation in mind.

Direct and Indirect Impact​

Direct filter impact means a saved filter references a space/project key, name, or category.

Indirect board impact means a board depends on an impacted saved filter.

Indirect dashboard impact means a dashboard gadget exposes an impacted saved-filter reference where metadata is available.

Use these signals as triage evidence before making Jira administration decisions outside Audit 360.