Skip to content

Instantly share code, notes, and snippets.

@shimuzhi
Last active March 30, 2026 14:45
Show Gist options
  • Select an option

  • Save shimuzhi/ecdd962e439267073f7738f5bfa45d9c to your computer and use it in GitHub Desktop.

Select an option

Save shimuzhi/ecdd962e439267073f7738f5bfa45d9c to your computer and use it in GitHub Desktop.
Getting Started for Page Review Manager for Confluence

Page Review Manager for Confluence Getting Started

Last updated: 2026-03-27

What the app does

Page Review Manager for Confluence helps a team keep one governed Confluence space current.

The current release supports:

  • one governed Confluence space per install
  • stale-page and due-soon detection
  • governed-space fallback owner defaults
  • space-level review queue
  • page-level review actions
  • scheduled background reevaluation
  • Confluence reminder comments
  • Jira follow-up creation or linking
  • audit history for review decisions

How to start

  1. Install the app into your Confluence Cloud site.
  2. Open the app from the target Confluence space sidebar.
  3. Activate the current space as the governed space.
  4. Choose a review cadence.

After activation, the app will show a review queue for the governed space.

How to use the dashboard

From the governed space page, reviewers can:

  • see stale, due-soon, and current pages
  • configure a fallback owner
  • configure Jira handoff for review work
  • review freshness and workflow state side by side
  • inspect recent audit activity
  • run a manual review check immediately

Configure ownership and Jira handoff

Open the governed space dashboard and scroll to Ownership and Jira handoff.

Fallback owner

Use the Fallback owner picker when you want unowned pages and stale-page escalations to route to one default reviewer for the governed space.

  • choose the person in Fallback owner
  • click Save owner and Jira settings
  • use Clear fallback owner and save if you want to remove the default owner again

If no fallback owner is configured, pages without a page owner remain visible in the Unowned queue until you assign or reassign them.

Jira handoff

Jira handoff is optional. When you want Request changes to create Jira follow-up automatically:

  1. Enter the Jira project key in Jira project key, for example DOC.
  2. Leave Jira issue type as Task or replace it with an issue type that exists in that Jira project.
  3. Click Save owner and Jira settings.

After the settings are saved, choosing Request changes from the page byline or review queue will create or update the linked Jira issue automatically.

How to use page-level actions

Open a Confluence page and click the review byline entry.

The current release supports these actions:

  • Approve
  • Request changes
  • Defer
  • Reassign

Each action updates the page review state and writes an audit entry.

If Jira handoff is configured for the governed space, Request changes will automatically create or maintain a linked Jira issue for the page.

The scheduled review loop continues to reevaluate the governed space and can leave reminder comments on pages that still need action.

Current release limits

The current release does not yet support:

  • multiple governed spaces per install

Responsible use

Before rolling the app into a broader documentation workflow, evaluate the current feature set and configuration in one governed space and confirm that the resulting review states, reminder comments, and Jira handoff behavior fit your process.

Customers remain responsible for:

  • reviewing page accuracy before acting on app output
  • deciding whether a workflow state or reminder should trigger operational action
  • ensuring app use matches their own legal, regulatory, and records-management obligations

Support

Use the Marketplace support link or email support@nagayasu.work.

To help us reproduce the issue quickly, include:

  • your Atlassian site URL
  • the governed space key or name
  • the page URL, if the issue is page-specific
  • the Jira project key, if Jira handoff is enabled
  • the expected result and the actual result
  • screenshots or screen recordings when available
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment