Currently, the Jira Legacy Issues macro in Confluence allows exporting Jira issue tables to Word/PDF with all issues and fields included. This is a critical feature for reporting, compliance, and stakeholder documentation.

The new Jira Work Items macro does not replicate this behavior. When exporting, the output is incomplete — issues are truncated, converted into images, or shown only as links. As a result, the export does not match what is displayed in the macro on the Confluence page.

Multiple users in the Atlassian Community have confirmed this limitation, and no workaround or app resolves it. Teams that depend on full exports are blocked by the deprecation of the legacy macro.

🔹 Business Impact

• Compliance & Audit: Full exports are required for external reporting and regulatory records.

• Efficiency: Teams must now leave Confluence and manually export from Jira, duplicating effort and breaking documentation flows.

• Continuity: With the legacy macro being deprecated by 2026, this gap creates a major regression in functionality.

🔹 Supporting Community References

• Exporting Jira issues w/ new Jira Issue macro vs legacy Jira

  “When exporting Jira issues with the new macro, the full list does NOT export. The table truncates into an image and we cannot export it as a full table the way the legacy macro did.”
  🔗 View discussion

• Insert Jira issues vs legacy version problems

  “Exported PDF however gives 3 links: The legacy version did display tables in the PDF, we are forced now to use the legacy version.”
  🔗 View discussion