Skip to main content

Spaces Audit

Spaces Audit is a read-only Audit 360 module for Jira administrators. It helps you review Jira spaces (called projects in Jira APIs), their ownership signals, activity signals, feature configuration, and governance findings. Use Spaces Audit before planning cleanup, ownership updates, or governance changes.

Audit 360 uses the word spaces in the customer experience. Jira APIs and some Jira administration screens may refer to the same area as projects.

When to Use Spaces Audit​

Use Spaces Audit when you need to:

  • Inventory all Jira spaces and review their key properties.
  • Find spaces with missing ownership or category signals.
  • Identify spaces with low activity or feature configuration inconsistencies.
  • Understand which saved filters, boards, and dashboards depend on each space.
  • Track and compare completed Spaces Audit runs over time.

What Spaces Audit Analyzes​

Spaces Audit examines normalized audit evidence from:

  • Jira space inventory — name, key, lead/owner, category, type, style, and archive state.
  • Activity signals — issue count and most recent issue update timestamp.
  • Feature configuration — which Jira features are enabled, disabled, or inconsistent on each space.
  • Direct filter dependencies — saved filters that reference a space by key, name, or category.
  • Indirect board dependencies — boards that depend on impacted saved filters.
  • Indirect dashboard dependencies — dashboard gadgets that reference impacted saved filters (where gadget metadata exposes filter references).
  • Governance findings — normalized evidence combined into actionable governance insights.

Risk Labels and Cleanup Candidates​

Spaces Audit assigns risk labels to help you prioritize review work:

  • High risk — spaces with direct filter dependencies, board or dashboard dependencies through filters, or missing owner with active usage.
  • Medium risk — spaces with missing category, inconsistent feature configuration, or low activity.
  • Low risk — spaces with only informational drift.

Cleanup candidates are spaces flagged as candidates for potential removal or archival based on low activity or other signals. These are informational review candidates only. Audit 360 does not delete, archive, or modify any spaces automatically.

What Spaces Audit Does Not Do​

Spaces Audit does not delete, archive, modify, or remediate Jira spaces. It does not introduce destructive actions or decision workflows that require approval.

Spaces Audit includes Audit Overview and Audit Details tabs. It does not include a separate cleanup decision or approval interface.

Spaces Audit does not store raw Jira API responses, work item keys, credentials, or secrets. Activity evidence is based on issue counts and most recent update timestamps only.

Relationship with Audit Library​

Completed Spaces Audit runs appear in Audit Library. Loading a saved run restores the stored result and does not rerun the audit or refresh evidence from Jira. This allows you to track historical results and compare findings across multiple audit runs.

Next Steps​