nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Confluence Jira macro suddenly showing “Jira Data Center macro no longer supports work items from Ji

Rinkesh Patel

Hi Atlassian Community,

We have existing Confluence Cloud pages that have been displaying Jira Cloud work items successfully using Jira macros and JQL filters.

These previously working pages have suddenly started displaying the following message:

“Jira Data Center macro no longer supports work items from Jira Cloud. Use the Jira Work Item macro instead. Contact support if you have questions.”

We also see:

“No Jira Data Center site is configured. Ask a site administrator to add a Jira Data Center application link.”

No changes were made to the affected JQL filters or Confluence pages from my side.

Has anyone experienced this change with existing Confluence Cloud pages?

Specifically:

Why would an existing Jira macro that previously displayed Jira Cloud work items suddenly be treated as a Jira Data Center macro?
Is there a supported way to restore the existing functionality without manually replacing the macros on all affected pages?
Should existing macros have been automatically migrated to the Jira Work Items macro?

Any guidance would be appreciated. Thank you.

Accepted answers

All comments

Mikael Sandberg

Hi @Rinkesh Patel,

Welcome to Atlassian Community!\

This is expected, Atlassian announce back in April that the legacy Jira macro will be deprecated, you can see the announcement here:

https://community.atlassian.com/forums/discussion/3126604/the-jira-legacy-macro-is-becoming-the-jira-data-center-macro

For cloud there is a new macro called Jira Work Items that replaces the old Jira macro.

Rinkesh Patel

Hi Mikael,

Thank you for the clarification and for sharing the announcement.

I noticed that the announcement states that existing Jira Legacy macros used to insert Jira Cloud issues on cloud editor pages would be automatically converted to Jira Work Items, and that no customer action is required.

In our case, the existing macro does not appear to have been automatically converted and is instead showing the Jira Data Center macro error.

Do you know why an existing macro might not have been automatically converted, or whether there is a recommended way to address this without manually replacing the macro?

Thank you for your help.

Rinkesh Patel

One additional concern is the existing customer experience and look and feel. Our users are accustomed to the current layout and presentation of Jira results within our Confluence pages.

Is there a way to migrate to Jira Work Items while preserving the existing table layout, columns, formatting, and overall user experience as closely as possible?

I also noticed that the announcement states existing Jira Legacy macros using Jira Cloud would be automatically converted. In our case, the macro appears not to have converted successfully and is instead showing the Jira Data Center macro error.

Could you please advise on both the automatic conversion issue and preservation of the existing layout?

Gabriela - LeanZero

Hi Rinkesh, I think both messages are simply what the cloud editor now shows for an old Jira macro that the conversion missed, because your first one even says the items come from Jira Cloud, and going by the announcement those pages should have been converted for you.

There's one documented way that happens, and you can see it in the page history. If you open an affected page's history, look for a version called "Automatic conversion: Legacy Jira Issue Macro to Smart Link List View", which may be listed as Anonymous. If a later version from a person follows it, an old unpublished draft put the legacy macro back when it was published, which is an open bug (https://jira.atlassian.com/browse/CONFCLOUD-85172). Restoring the converted version brings your work items list back, but you'll need to redo whatever that later edit changed.

If you don't see a conversion entry at all and the content came over in a migration, Jira Macro Repair re-points old macros at System Jira (https://confluence.atlassian.com/confkb/using-the-jira-macro-repair-1084362152.html), and the announcement's FAQ says they're then converted automatically.

With a lot of pages I'd raise it with Atlassian Support rather than fix them one by one, since the error itself says to and Atlassian's update on this conversion asks for business-critical cases to go to Support with a link to that post (https://community.atlassian.com/forums/discussion/3241653).

To rebuild one by hand, you can type /jira, pick Jira work items, paste the same JQL, then choose your columns with the column icon and drag them into the old order (https://support.atlassian.com/confluence-cloud/docs/insert-the-jira-issues-macro/). I should warn you that your old column widths won't come across (https://jira.atlassian.com/browse/CONFCLOUD-84574) and you can't sort by clicking a header (https://jira.atlassian.com/browse/CONFCLOUD-77267).

Rinkesh Patel

Hi,

Thank you. I checked the page history and found the “Automatic conversion: Legacy Jira Issue Macro to Smart Link List View” version.

I compared that automatically converted version with our existing version, and the look and feel changes after the conversion. Our existing Jira tables use several custom fields and a specific column layout that our users rely on for reporting.

Is there any supported way to preserve the existing Jira Legacy macro table layout, custom-field display, column ordering, and formatting when converting to Jira Work Items?

Because we have multiple reporting pages using this setup, manually rebuilding each table and attempting to reproduce the existing layout would not be ideal.

Thank you again for your help.

Rinkesh Patel

Is there any Atlassian backend configuration, feature flag, tenant-level setting, or temporary exception that can re-enable Jira Cloud work items in the Jira Data Center macro for our Confluence Cloud site? We are specifically looking to retain the existing macro and configuration, not rebuild the pages using Jira Work Items.

Gabriela - LeanZero

Hi Rinkesh, thank you for checking the history, so we know the conversion did run on that page.

I'm afraid there's no opt-out. I couldn't find any setting, feature flag or tenant option that lets the old macro show Jira Cloud work items again, and neither Atlassian's announcement nor their update on this offers one. Restoring the version from before the conversion won't keep it either, because it only puts the legacy macro back with the same Data Center error you're seeing, and Atlassian says on CONFCLOUD-84619 that they "will continue converting content from the legacy Jira Issue Macro to the Jira Work Item Macro, even after a revert" (https://jira.atlassian.com/browse/CONFCLOUD-84619).

The good news is that your missing custom field columns are a known conversion bug. On CONFCLOUD-84576 the Confluence team says they've built an automated conversion for it and that Support can set it up for you (https://jira.atlassian.com/browse/CONFCLOUD-84576), and CONFCLOUD-84792 covers the same loss for older macros that came over from Server (https://jira.atlassian.com/browse/CONFCLOUD-84792). With several reporting pages I'd open a support ticket that names those tickets and lists your pages, and ask them for that automated conversion.

For a single page you don't have to rebuild the table, since you can restore the converted version and then use the column icon on the work items list to add your custom fields back and drag them into the old order. Your column widths still won't carry over, as I mentioned before.

CelesteCS

Hi, I'm Alexey 'Ce' from CelesteCS.

@Rinkesh Patel , as Gabriela said, there is no switch that brings the legacy macro back for Jira Cloud work items. If what your readers miss is a table whose layout you control, rather than the Smart Link list view, an app can give you that. With our CelesteCS Reporting for Confluence you keep your JQL or saved filter and define the table yourself:

A Reporting Jira Data Provider with your query, e.g. filter = 12345 or project = ABC AND status != Done ORDER BY priority DESC.
A Reporting Table View with one column per field, in the order you want, with your own headers: CurrentItem.key, CurrentItem.fields.summary, CurrentItem.fields.status.name, CurrentItem.fields.assignee.displayName, custom fields too.
Optional: calculated columns, Sum/Count footers, row highlighting, and Filters for readers, which gives everyone who views the page a search box, column filters and sorting.

The columns wrap like any Confluence table, so wide reports fit the page. Examples step by step:

The app is on the Atlassian Marketplace: CelesteCS Reporting for Confluence (free trial, Cloud and Data Center).

Welcome!

It looks like you're new here. Sign in or register to get started.