Jira to Confluence

Confluence publishing

Create or update management-report pages in Confluence directly from the StatusDeck Jira workflow.

StatusDeck for Jira CloudLast updated: 3 September 2026

How Jira and Confluence interact

StatusDeck reads authorised Jira delivery data, builds the report in the StatusDeck Forge app, and—only when the user explicitly chooses Publish to Confluence—uses the current Atlassian user context to create/update Confluence content and attachments.

Confluence is optional for normal StatusDeck reporting.

Prerequisites

  • StatusDeck installed and accessible in Jira Cloud.
  • A generated Sprint or Project/Program report.
  • Confluence available to the current Atlassian user.
  • The current user can access the destination Confluence space/parent page and has permissions needed to create/update the report page and attachments.

Publish a report

  1. Generate the StatusDeck report from Jira.
  2. Select Export / Publish.
  3. Select Publish to Confluence.
  4. Select a Confluence Space.
  5. Select a Parent Page.
  6. Enter the Sprint child page title or Project / Program page title.
  7. Select Publish to Confluence.

What StatusDeck publishes

  • Creates the report page beneath the selected parent when it does not already exist.
  • Updates the same report page on later publishes using the selected destination/title.
  • Writes native StatusDeck report content to the Confluence page.
  • Attaches a branded PDF executive report.
  • Attaches an editable PowerPoint report.
  • Uses stable PDF/PPT filenames so Confluence can maintain attachment version history on republish.

Custom Jira Insights in Confluence

Where configured, portable Custom Jira Insights are represented in Confluence using appropriate page content such as tables, panels or uploaded visual assets. The attached PDF and PowerPoint remain the full-fidelity companion outputs.

User-context permissions

Publishing runs as the current Atlassian user. StatusDeck is not an administrative bypass: only Confluence spaces/pages available to that user can be selected, and Confluence enforces the user’s content and attachment permissions.

Publication metadata

After a successful publish, StatusDeck stores a small Forge KVS publication record such as destination, page identifier/title/URL, space information, attachment filenames, publish time and publishing user-context identifier. The report files themselves stay in Confluence.

Marketplace reviewer

For deterministic Marketplace review steps and expected results, use Jira ↔ Confluence testing.

Documentation baseline: 3 September 2026. This documentation describes the current submitted StatusDeck capability set and is updated when material product, permission, storage or security behaviour changes.