StagBane
Get it on the Marketplace

Changelog

All notable, customer-visible changes to StagBane. Dates are Atlassian Marketplace release dates.

v1.0- First public release (pending submission)

The first release of StagBane- Page Health Auditor for Confluence. Built entirely on Atlassian Forge and carries the Runs on Atlassian badge.

Triage memory, cadence, ownership, and a weekly digest

Four additions that make the queue quieter and the workload clearer. All non-destructive, all admin-only, and still nothing leaves Atlassian.

  • Dismiss a reason (suppression memory). Acknowledge a specific reason on a page- "yes, this is old, and that's fine"- and it stops cluttering the queue. A dismissed reason comes back on its own if the page is edited or that reason changes (a new broken link, an owner departing), so nothing stays hidden once the situation moves. Dismiss every reason on a page and it moves to a Dismissed filter; the page's band underneath is unchanged, and dismissals never affect the reader trust badge, the Rovo-readiness score, or the agent. Each dismiss/restore is recorded in an in-app audit log with who, when, and an optional note.
  • Per-space review cadence. Override the global review window for individual spaces- a fast-moving policy space can be reviewed every 90 days while a stable reference space stays at a year. Saving re-ranks pages immediately.
  • Group the queue by owner. A Group by owner toggle clusters the queue by page owner, with a header and band counts for each owner and an Unassigned bucket at the bottom- so "who owns the most stale pages" and "what has no owner at all" are visible at a glance.
  • Weekly digest. An admin-facing "docs we would not trust" digest, grouped by owner, with new-since-last-week and resolved-since-last-week counts. It is taken automatically each week and shown in the queue (you can also generate one on demand). It is in-product only- no emails are sent and nothing is posted to your pages.

Review queue (admin-only)

  • An admin-only review queue in Confluence → Settings → StagBane, ranking every page in your audited spaces by staleness.
  • Admin-selected audited spaces- StagBane scans nothing until an admin chooses spaces, so personal and archive spaces never flood the queue.
  • A daily incremental scan: the first scan of a space reads each page once to build a link map; after that, only changed pages are re-read. A live status line shows scan progress and per-space page counts.
  • Filters for space, band, and review state- the space and band filters are searchable multi-selects (the space search matches name or key); a Needs review worklist filter; and an Excluded view for pages opted out with pha-evergreen. Paginated at 25 rows per page.
  • Show/hide columns- a Columns picker keeps optional columns out of the way (the page title and row actions always stay); the choice is saved per site.
  • Settings (the gear in the header): choose audited spaces, set the review window (how long a Verified Current review stays current, 30–1095 days), set the daily Request Budget, set the request-escalation window (how long an unanswered review request waits before an at-risk page escalates to Critical, 1–90 days, default 7), rescan now, and export the current audit to CSV.

Staleness signals and banding

  • Five plain signals behind every ranking: page age, owner missing/inactive, review recency, orphaned (no links from other audited pages), and broken internal links.
  • Four bands- Critical, Stale, Watch, Healthy- assigned by an ordered set of rules; the highest-precedence rule that matches sets the band. No hidden score. Compound rules escalate to Critical when problems stack- a stale page that also has broken links or also has no owner, and (with no age requirement) any page with broken links and no owner, so a fresh page already pointing at deleted pages with nobody to fix it is Critical. An at-risk page whose review request goes unanswered past the escalation window also escalates to Critical, treating an unresponsive owner as effectively absent.
  • Every row shows the rule that placed the page there and lists every signal that fired, so any page's ranking can be explained in one sentence and broken down in full. The Request Owner Review comment lists the same full set of reasons.
  • Worth a closer look- a shortlist of pages that rank Healthy or Watch but whose titles suggest they may be dated (a past year, or words like draft, legacy, deprecated). These are nominations for a closer read, not freshness judgments.

Queue actions (all non-destructive)

  • Mark Current- records today as the page's review date and labels it verified-current; toggles to ✓ Current. Re-bands the page toward Healthy on the next scan.
  • Needs review- a private triage marker (needs-review label); notifies no one and never affects a page's band.
  • Request Owner Review- posts one templated comment @mentioning the page's owner, asking them to review. Governed by a daily Request Budget (default 25 per site, adjustable 1–100) so review requests can never become a notification storm. Blocked, with the reason shown, when there's no reviewable owner, a request is already open, or the budget is spent.
  • Resolve by reply- the owner can answer the review-request comment with Verified or Stale to resolve it without opening the queue. Verified marks the page Verified Current and closes the request; Stale records a human stale verdict that overrides the automatic signals. Only the page owner can resolve from the thread; anyone else is pointed to the owner. StagBane confirms each outcome with a reply.
  • Audit- opens the Page Health Auditor (Rovo agent) for a content-level second opinion on the page.
  • StagBane never archives, deletes, or rewrites a page. Every action is one a human triggered.

Rovo agent- Page Health Auditor

  • An on-demand agent in Rovo chat that audits one page for staleness, compares two pages for contradictions, and finds overlapping pages on a topic (returned as candidates to compare, never as verdicts).
  • Reads as the invoking user- it sees only what that user can already access, with no elevated access of its own.
  • Grounded in the queue- when a page is in the index, the agent cites the queue's band and reason, then adds its own content read, and explains where the two diverge (a Healthy-banded page whose content is actually dated, or a Stale-banded page that only tripped a broken-link rule).
  • Acts on your confirmation- it can trigger the same non-destructive queue actions for you (mark a page current or stale, request an owner review, set the needs-review label). It always states what it will do and waits for your explicit yes, checks your permissions (page owners can self-resolve; site admins can do all), and never edits, archives, or rewrites content.
  • Lists stale pages for site admins- ask "which pages are stale?" and an admin gets the queue's ranked list right in chat; non-admins are pointed to the queue.
  • Audits several pages on request- "audit them all" works through the list, up to five per reply, then offers to continue (or one at a time, your choice).
  • Every verdict cites specific evidence and names the page version it judged. Verdicts are chat-only- never stored and never written back to the queue.
  • Launchable one-click from any queue row or Worth a closer look item, or directly in Rovo chat.

Privacy and trust

  • No external servers and no external network calls- the app makes no requests outside Atlassian.
  • No telemetry or analytics- your content never leaves Atlassian, not even as metrics.
  • Page bodies are read only to extract internal links and then discarded. Stored data is limited to page metadata, computed signals and bands, page-to-page link relationships, scan status, and the review-request log- never page body text.
  • The Rovo agent's verdicts are never stored.
  • No Personal Access Tokens are required or used.
  • See Privacy & data for the full breakdown, including how restricted pages are handled and what remains after uninstall.

Known limitations

  • Orphan and broken-link detection are scoped to audited spaces. Links to external sites, and links into spaces you didn't audit, are never checked. A page can look orphaned or broken simply because the space on the other end of a link isn't audited.
  • The Rovo agent audits up to five pages per reply. For a longer list it does the most critical five, then offers to continue. The site-wide ranked view is the review queue (and, for site admins, the agent's "which pages are stale?" list).
  • The Rovo agent changes nothing without your confirmation. Its verdicts are advisory and never auto-applied; even when you ask it to act, it only triggers the queue's non-destructive actions (a label, a review date, a comment), never your page content.