Testing Jira ↔ Confluence interaction

Purpose of this guide

This page is written for Atlassian Marketplace reviewers and customer administrators who need to test the interaction between Jira and Confluence. It focuses on observable product behaviour and expected results.

Test setup

• Install/enable StatusDeck in a Jira Cloud site.
• Use a Jira project with at least one Scrum board and Sprint containing visible work items.
• Ensure Confluence is available to the reviewer’s Atlassian user.
• Create or identify a Confluence space and a parent page where the reviewer can create child pages and attachments.

Scenario 1 — First Jira → Confluence publish

1. Open StatusDeck from Jira.
2. Select a project, Scrum board and Sprint.
3. Generate the Sprint report.
4. Confirm the report renders Jira-derived delivery data.
5. Open Export / Publish.
6. Select Publish to Confluence.
7. Select an accessible Confluence Space.
8. Select a Parent Page.
9. Enter a new Sprint child-page title, for example StatusDeck Review - Sprint 1.
10. Select Publish to Confluence.

Expected result

• A report page is created beneath the selected parent.
• The page contains native StatusDeck report content.
• A PDF report is attached.
• An editable PowerPoint report is attached.
• StatusDeck shows a successful publication state/link where available.

Scenario 2 — Republish the same report

1. Change visible Jira delivery data (for example update a test work item status) or edit/publish Management Commentary.
2. Regenerate/refresh the StatusDeck report.
3. Publish again using the same Confluence Space, Parent Page and report-page title.

Expected result

• StatusDeck updates the existing report page rather than intentionally creating a new page for the same destination/title.
• The page content reflects the latest published report.
• Stable PDF/PPT attachment filenames allow Confluence to maintain attachment version history.

Scenario 3 — Permission boundary

1. Use a reviewer account that has access to one Confluence space but not another.
2. Open the StatusDeck Confluence publishing destination selector.

Expected result

StatusDeck operates in the current Atlassian user context. It should not provide an administrative bypass to inaccessible Confluence content. Confluence permission errors should prevent unauthorised publication.

Scenario 4 — Project / Program publish

1. Select a Jira project with multiple reportable Scrum boards.
2. Generate the Project / Program report.
3. Open Export / Publish → Publish to Confluence.
4. Select the test space/parent and enter a Project / Program page title.
5. Publish.

Expected result

The Confluence page contains Project/Program management content such as Executive & Program Health, Management Commentary and cross-team delivery evidence, with PDF and PowerPoint attachments.

Scenario 5 — Custom Jira Insight

1. Configure a supported Custom Jira Insight using a saved filter, supported dashboard gadget or custom JQL.
2. Generate the report and confirm the insight appears in StatusDeck.
3. Publish the report to Confluence.

Expected result

The custom insight is represented in the published Confluence report when portable, and remains available in the full PDF/PowerPoint output.

Scopes used by this interaction

The current manifest requests Jira read scopes for report generation plus Confluence scopes for space/page discovery, page creation/update and attachments. See Permissions & scopes for the current manifest-aligned list and purpose of each scope.

Reviewer support

If a test step cannot be completed, contact marketplace@qtilabs.com with the Jira/Confluence step, the observed message and a screenshot that does not contain unnecessary sensitive customer data.