Skip to main content

Spaces Audit Details

Audit Details shows the full normalized evidence table for a loaded Spaces Audit run. Use this view to review one space at a time, triage governance findings, and inspect evidence in depth.

The Details Table​

Audit Details includes:

  • Run identity — loaded run name, completion timestamp, and who ran it.
  • Evidence summary — counts of total findings, filter impacts, and governance findings from the audit.
  • Paginated spaces table — one row per space, grouped by columns:
    • Space — space name, key, and ID
    • Inventory — owner, category, project type, project style, and archive status
    • Activity — issue count, last update date, and activity state
    • Features — counts of enabled, disabled, and inconsistent feature configuration
    • Filter impact — counts of direct and indirect impacts and governance findings
    • Risk — risk level (High, Medium, or Low)
    • Inspect — action to open space inspection

Sort the table by any column (Space, Activity, Risk) to focus your review. Use the page size selector to show more or fewer rows at once.

Coverage Notes​

At the bottom of Audit Details, coverage notes explain non-blocking warnings and partial data visibility. For example:

  • Dashboard coverage may be limited — dashboard gadget metadata does not always expose saved-filter references, so some dashboard dependencies may not be detected. This is a known limitation of the dashboard gadget endpoint, not a missing Audit 360 feature.
  • Board coverage may be partial when Jira APIs or permissions restrict visibility.
  • Feature configuration may be unavailable for some spaces if Jira does not expose feature state.
  • Activity may be incomplete if issue search permissions limit visibility to some projects.

Coverage notes do not mean Audit 360 changed Jira. They explain what audit data may be incomplete so you can make informed decisions when reviewing results. All audit operations are read-only.

Inspect View — Deep Dive into One Space​

Click the Inspect button on any row to open a modal inspection view for that space. The inspection view shows organized evidence:

  • Execution details — metadata about when and how the audit was run.
  • Space profile — space name, key, ID, owner, category, type, style, and archive state.
  • Governance and activity — issue count, days since last activity, risk level, risk reasons, and cleanup candidate status.
  • Feature configuration — enabled, disabled, unknown, and inconsistent Jira features for this space, plus any feature configuration findings.
  • Direct filter impact — saved filters that directly reference this space by key, name, or category.
  • Indirect board impact — boards that depend on impacted filters.
  • Indirect dashboard impact — dashboards with gadgets that reference impacted filters.
  • Governance findings — all normalized governance findings for this space (this section is omitted entirely if there are no governance findings).

Evidence tables within each section show detail rows only (no pagination, since each section is scoped to one space). Empty sections show explicit "no evidence" states, except for Governance findings, which is omitted entirely when there are zero findings.

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

Understanding Impact Types​

Direct filter impact — A saved filter's JQL (search criteria) includes a reference to this space's project key, project name, or project category.

Indirect board impact — A board uses a saved filter that has a direct impact on this space. If that filter is removed or changes, the board is affected.

Indirect dashboard impact — A dashboard gadget displays results from a saved filter that has a direct impact on this space. If that filter is removed or changes, the gadget may show different results. Note that this detection requires the dashboard gadget metadata to explicitly expose filter references — not all dashboard gadget types provide this metadata, so coverage may be partial or zero for some dashboards.

Use these signals as evidence when making Jira administration decisions. They help you understand what tools and workflows may be affected by space changes. If you see no dashboard impact evidence but expect dashboards to be affected, check whether those dashboards use gadget types that don't expose filter references in their metadata.