Skip to content

Confluence Features

BMAtlassian leverages Confluence beyond basic page creation. This guide covers the advanced features used across workflows.

Page Hierarchy

Artefacts are automatically organized under phase-specific parent pages:

Project Root
+-- Phase 1: Analysis
|   +-- Research Report
|   +-- Product Brief
|   +-- Brainstorming Session
+-- Phase 2: Planning
|   +-- PRD
|   +-- UX Design
+-- Phase 3: Solutioning
|   +-- Architecture
|   +-- Implementation Readiness
+-- Phase 4: Implementation
    +-- Sprint Status
    +-- Retrospective: Epic-1
    +-- Project Dashboard

Phase parent pages are created automatically on first use. Their IDs are cached in .jira-key-map.yaml under confluence_pages.phase_parents.

Comment System

Inline Comments

Used by validation and review workflows to post findings on specific sections of a page:

  • PRD Validation -- posts inline comments on sections that need improvement, with severity and recommendations
  • Adversarial Review -- posts findings directly on the text where issues were found
  • Document Validation -- section-specific quality feedback

Used for summary results that apply to the entire page:

  • Validation verdicts (PASS / PASS WITH NOTES / NEEDS REVISION)
  • Editorial review findings tables
  • Structural reorganization proposals

Comment History Tracking

Review workflows check for existing comments before posting new ones:

  1. Retrieve existing inline comments via getConfluencePageInlineComments
  2. Count open vs. resolved findings from previous reviews
  3. Include review history in the new footer comment
  4. Avoid duplicating findings that already exist

This creates a traceable review history on each page.

Project Dashboard

The project dashboard (/bmad-atlassian-project-dashboard) creates a single Confluence page showing:

  • Phase progress -- which artefacts exist across all 4 phases
  • Epic/Story status -- per-epic breakdown of story completion
  • Sprint status -- active sprint progress from JQL queries
  • Recent activity -- latest Jira transitions and Confluence updates
  • Review findings -- summary of open vs. resolved findings across all reviews

The dashboard is updated automatically by the post-handoff task and can also be refreshed manually.

Labels

BMAtlassian uses Confluence labels for artefact discovery:

Label Artefact
bmad-research Research reports
bmad-brief Product briefs
bmad-brainstorming Brainstorming sessions
bmad-project-context Project context documents
bmad-prd Product Requirements Documents
bmad-ux UX Design specifications
bmad-architecture Architecture decision documents
bmad-readiness Implementation readiness reports
bmad-retrospective Epic retrospectives
bmad-dashboard Project dashboards
bmad-documentation Generated project documentation

Agents search for artefacts using CQL label queries (e.g., label = bmad-prd AND space = PROJ).

CQL Queries

BMAtlassian uses Confluence Query Language for artefact discovery:

# Find the PRD for this project
label = bmad-prd AND space = "{confluence_space_key}"

# Find previous retrospectives
label = bmad-retrospective AND space = "{confluence_space_key}"

# Check if a page already exists by title
title = "{page_title}" AND space = "{confluence_space_key}"

# Find all BMAD artefacts under a parent
ancestor = {parent_page_id} AND label in (bmad-prd, bmad-architecture, bmad-ux)