Skip to main content
Nerve Centre KPIs · Audit Profile · Sentiment Settings Surfaces the daily questions an Atlassian-suite team lives with when audit findings are routed to Confluence as evidence-rich wiki pages: is the token still good and the Findings Space readable, is the page-properties scheme intact, are findings being closed or quietly going stale, and (for merchants who also run Jira) are the Confluence pages and linked Jira issues in sync?

​
What this audit checks

​
Authentication & access

  • API token still valid (auth on /wiki/rest/api/user/current)
  • Mapped Findings Space exists and is not archived
  • Integration user can read + write pages in the Findings Space (no page restrictions excluding it)
  • Atlassian rate-limit (cost-budget) headroom > 30%

​
Findings-Space integrity

  • Finding-pages carry the vortexiq-finding label and a vortexiq.status page-property
  • Page-properties macro present on every finding-page (deleted macro = page falls out of all counts)
  • Wrong-Space drift - findings being written to a Space the connector is not pointing at
  • Draft / trashed / archived finding-pages excluded from open counts correctly
  • Open finding-page count vs 30-day baseline (sudden growth = drowning signal)

​
Finding lifecycle (the stickiness test)

  • Abandoned findings - vortexiq.status open AND version.when unchanged >14d
  • Finding resolution rate over rolling 90d (target >75%)
  • Avg time-to-fix for resolved findings, by vortexiq.priority
  • Findings closed wont_fix without a comment (silent dismissals)
  • Regression rate - findings reopened after a closed status

​
Team capacity

  • Assignees with >10 open finding-pages via vortexiq.assignee (overload signal)
  • Unassigned finding-pages > 5 (work nobody owns)
  • Blocked finding-pages count + change WoW
  • Backlog-by-priority skew (mostly low = no one is grooming)

​
Cross-connector signals

  • Critical findings from sibling connectors (shopify/bigcommerce/adobe/cybersource) older than 7 days with no Confluence finding-page - coverage gap
  • Confluence-vs-Jira sync drift - finding-page vortexiq.status and the linked Jira issue status disagree (>2-3 rows) for Atlassian-suite merchants
  • Finding-pages referencing decommissioned / archived integrations - stale work

​
Severity thresholds

SignalWarnCritical
vortexiq_findings_abandoned515
vortexiq_finding_resolution_rate7550
blocked_tickets38
unassigned_tickets520
oldest_open_ticket_age_days6090
open_findings_vs_baseline_pct50100
rate_limit_headroom_pct3010

​
Data sources

  • GET {site_url}/wiki/rest/api/user/current - Token + integration-user account info
  • GET {site_url}/wiki/api/v2/spaces - Resolve mapped Findings Space + archived-Space check
  • GET {site_url}/wiki/api/v2/pages - List finding-pages (label + space filter) for open/blocked/by-status/by-priority/throughput
  • GET {site_url}/wiki/api/v2/pages/{id}/properties - Read vortexiq.status / vortexiq.priority / vortexiq.assignee page-properties
  • GET {site_url}/wiki/rest/api/content/search?cql=... - CQL reconciliation (abandoned / created-in-window / wrong-Space drift)