Skip to content

Release Notes — 2026 03 27

This release introduces Change Sets for multi-page review bundles and a full REST API for programmatic access.

  • Group related page changes into a named change set with a shared title, summary, and external reference URL (e.g., a GitHub PR link).
  • Version-aware rollup state computed automatically across all pages in a change set: open, in_review, partially_approved, all_approved, has_rejections, stale.
  • Per-page version tracking within change sets: current version, approved version, stale detection, and version delta.
  • Bulk submit all eligible pages in a change set for approval in one action with per-page success/failure reporting.
  • Preflight (dry-run) evaluation checks submission eligibility without writing data — ideal for CI/CD validation.
  • Change set context in page comments — When pages are submitted through a change set, the Confluence page comment includes the change set title, summary, and a clickable reference URL.
  • Archive completed change sets to mark them as read-only.
  • 9 API endpoints for change set and page operations via Atlassian Forge apiRoute.
  • 3-legged OAuth (3LO) authentication with custom scopes for granular access control.
  • Endpoints: List, create, update, archive, detail, submit, and preflight for change sets. Submit and preflight for individual pages.
  • Audit traceability — All API actions are marked (via API) with the OAuth client ID recorded in the audit trail.
  • Real user identity — API callers are authenticated via Atlassian OAuth; the authenticated user’s account is used for all actions.
  • Change Sets tab in the space dashboard with rollup state lozenges and per-page detail modal.
  • Improved tree table in Manage Space with proper icons and children existence probing.