The Jira Legacy macro is becoming the Jira Data Center macro

[#1]

Hi Atlassian Community,

We are announcing that on April 9th, 2026 (6 months from now), for Confluence Cloud, the Jira Legacy macro will become the Jira Data Center macro in the cloud editor. This means that:

• Jira Legacy macro (also known as Jira Issue Macro) will no longer support the insertion of Jira Cloud issues. Customers can instead use the new and improved Jira Work Items (also known as Jira List of Links/SLLV) to insert Jira Cloud issues.

• Customers using Confluence Cloud and Jira Data Center will still be able to use the Jira Legacy macro (now called Jira Data Center) to insert Jira Data Center issues.

• Customers who are not using the cloud editor, and are still using the legacy editor will still be able to use Jira Legacy macro to insert both Jira Cloud and Jira Data Center issues until legacy editor is deprecated.

Jira Work Items: Experience Upgrades and Key Feature Parity

We’re also upgrading Jira Work Items to provide a better and more intuitive experience by addressing key feature gaps from the Jira Legacy macro. This will enable teams to confidently manage Jira items in Confluence as we move toward a unified and modern integration. We will address the following tickets:

• ConfCloud-77443: Jira Work Items will be displayed within the body of content macros as tables.

• ConfCloud-77510: Jira Work Items will display images from Jira Issues.

• ConfCloud-77556: Jira Work Items will support rich text in displayed fields.

• ConfCloud-77661: We will enable Jira Work Items to include all listed issues in Word/PDF exports.

Detailed Plan

Starting April 9th, 2026,

• The Jira Legacy macro will become Jira Data Center macro. Customers will no longer be able to insert Jira Cloud issues with it.

• Existing instances of the Jira Legacy macro used to insert Jira Cloud issues on cloud editor pages will be automatically converted to the new and improved Jira Work Items.

FAQ

Can you make sure that Jira issues supports rendering in bodied macros (CONFCLOUD-77443) before the Jira Legacy macro becomes Jira Data Center?

• Yes, we plan to resolve this issue before the Jira Legacy macro becomes Jira Data Center.

What happens to Jira Legacy macros when a legacy editor page is converted to the cloud editor?

• Once the page is converted to the cloud editor, Jira Legacy macros used to insert Jira Cloud issues will be automatically converted to Jira Work Items. Jira Legacy macros used to insert Jira Data Center issues will remain untouched.

What if the Jira Macro Repair tool is used to update links of existing Jira Legacy macros from a Jira Data Center link to a Jira Cloud link?

• Those Jira Legacy macros will automatically be converted into Jira Work Items.

Note

No customer action is required. All updates and conversions will happen automatically during the transition. The experience of Data Center sites in the Jira Legacy macro will remain the same.

[Jens Müntinga]

Hello,

Am I the only one who finds it problematic that the Jira Legacy Macro is being phased out?

The legacy macro provides a clear and readable overview of issues, whereas the Jira Work Items macro presents tickets in a contained view that requires separate scrolling within the page just to see all issues that are supposed to be displayed.

From a UX perspective, this is a serious step backwards. Having a page with its own scrollbar and an embedded macro that introduces an additional scrollbar is, in my opinion, a clear UX design anti‑pattern.

This is also the reason why the Embed Database macro is practically unusable — it follows the same concept and suffers from exactly the same issue.

Overall, this feels visually unappealing and represents a real degradation of usability for users who rely on Confluence pages to present Jira ticket overviews in a clean and readable way.

Kind regards
Jens