Spaces Audit
Spaces Audit is a read-only Audit 360 module for Jira administrators. It helps you review Jira spaces/projects, ownership signals, activity signals, configuration signals, and governance findings before cleanup, ownership updates, or governance planning.
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:
- Review the inventory of Jira spaces/projects.
- Find spaces with missing ownership or category signals.
- Identify spaces with low activity or configuration drift.
- Understand saved filter, board, and dashboard dependencies before planning changes.
- Keep completed Spaces Audit runs available in Audit Library.
What Spaces Audit Reviews
Spaces Audit analyzes normalized audit evidence from:
- Jira space/project inventory, including key, name, category, type, style, archive state, and lead/owner where Jira exposes it.
- Count-only activity signals and latest activity timestamp where available.
- Project feature configuration where Jira exposes it.
- Saved filters whose JQL references a space/project key, name, or category.
- Boards that depend on impacted saved filters.
- Dashboard gadgets that expose impacted filter references where metadata is available.
- Governance findings derived from normalized audit evidence.
Risk labels help administrators triage review work. High risk can include direct filter dependency, board dependency through an impacted filter, dashboard dependency through an impacted filter, or missing owner while the space has usage. Medium risk can include missing category, inconsistent feature configuration, or low activity. Low risk can include informational drift.
Risk labels and cleanup candidates are review indicators only. They do not trigger automatic remediation.
What Spaces Audit Does Not Do
Spaces Audit does not delete, archive, modify, or remediate Jira spaces/projects. It does not introduce destructive actions.
Spaces Audit launch scope includes Audit Overview and Audit Details. It does not include a separate cleanup decision workflow.
Spaces Audit does not store raw Jira API payloads, work item keys, credentials, secrets, or tokens. Activity evidence is count-only and latest-update based, and raw Jira API payloads are not displayed.
Relationship with Audit Library
Completed Spaces Audit runs appear in Audit Library where supported by the app. Loading a Spaces Audit run restores the stored result and does not rerun the audit or refresh evidence from Jira.