Spaces Audit Limitations

Spaces Audit depends on Jira APIs, app permissions, and metadata available at audit time. Results are designed for administrator review, not automatic remediation.

API and Permission Coverage

Jira project lead is used as the owner signal where Jira exposes it. If Jira does not expose a lead or related metadata to the app, ownership coverage can be incomplete.

Board and dashboard dependency coverage may be partial when Jira APIs or permissions restrict visibility.

Feature consistency is best-effort and depends on Jira project feature API availability.

Activity Signal Limitations

Activity uses count-only and latest-update signals. Audit 360 does not store work item keys or raw work item payloads for Spaces Audit.

Latest activity can be unavailable or partial when Jira search visibility, permissions, or data availability limit the signal.

Dashboard and Board Impact Limitations

Dashboard impact depends on dashboard gadget metadata exposing saved-filter references. If a gadget does not expose a saved-filter reference, Audit 360 may not be able to connect that dashboard to a space impact.

Board impact is based on boards that depend on impacted saved filters. Coverage can be partial when board metadata is unavailable to the app.

Cleanup Candidate Limitations

Cleanup candidates are informational review candidates only. They do not recommend an automatic delete, archive, or remediation action.

Read-Only Scope

Spaces Audit does not delete, archive, or change Jira spaces/projects. It does not modify Jira configuration, saved filters, boards, dashboards, or work items.