Goal

Manual, on-demand PDF export of the approval state, available from a Jira work item and a Confluence page, using the same generation engine as the automated export.

Trigger

• Action available from the context menu (...) of the work item / page.

• Button label: "Export approvals to PDF".

Document layout

1. Header: work item / page identity (key, title) and generation date.

2. Approvals: status, progress, participants, decisions, comments, timestamps.

3. Work item / page data: selected fields.

4. Description.

Confluence: additional behaviour

• If the page already has an embedded approvals-list macro in its content, the export does not add a second list (no duplication).

• The approvals list embedded in the page content (macro) must be adapted so it renders correctly and is exportable to PDF via Confluence's built-in tools (native page export), independently of our export action.

Out of scope (follow-up)

• Defining templates and choosing a template at export time: a separate, later stage.

Acceptance criteria

• The "Export approvals to PDF" action is available from the context menu (...) of a work item and a page.

• The generated PDF contains, in order: header, approvals, work item / page data, description.

• Works for a single and for multiple approval paths on one work item / page.

• Exporting a Confluence page that has an embedded approvals list does not duplicate the list.

• The embedded approvals list renders correctly and is included in the native Confluence page export to PDF.