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; } } }

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

Tara Conklin_esvt7l

We noted the old legacy Jira Issues macro in Confluence will be fully deprecated by 2026. However, when exporting Jira issues with the new macro, the full list does NOT export. The table of items truncates into an image and we have not found a way to export it as a full table the way the legacy macro does. I've include two screenshots of the same Jira query with both Jira issues macros and you can see how the new macro exports the data.

QUESTION:

is it possible to export the new jira macro data as a complete table, similar to the legacy macro? This is ESSENTIAL for our business because we are contractually required by the FDA and other Federal agencies to provide PDF and/or Word documents of our lab research and this must include a complete list of our Jira data and certain fields.

Thank you for taking the time to read and respond. Please reach out at tara.conklin@neogenomics.com

Sincerely,

Tara Conklin

LEGACY JIRA ISSUES EXPORT

Screenshot 2025-07-09 at 10.12.09 AM.png

NEW JIRA ISSUES MACRO EXPORT

Screenshot 2025-07-09 at 10.11.55 AM.png

Accepted answers

Tomislav Tobijas

Hi @Tara Conklin ,

I believe this is a current limitation of the new macro.

I've tried looking for reported suggestions/bugs on JAC and managed to find this: CONFCLOUD-77070: Enhancing Jira Issues Macro in Confluence Cloud to fully display multi-line text fields from Jira (feel free to check other items as well)

I'd say a workaround is using the legacy macro and I hope this will be resolved until the deprecation of the old one in 2026 👀

I would suggest leaving a vote on this (or other relevant) suggestion, together with a comment about your use case/requirement, so that's taken into consideration as well.

Cheers,
Tobi

All comments

Tomislav Tobijas

Hi @Tara Conklin ,

I believe this is a current limitation of the new macro.

I'd say a workaround is using the legacy macro and I hope this will be resolved until the deprecation of the old one in 2026 👀

I would suggest leaving a vote on this (or other relevant) suggestion, together with a comment about your use case/requirement, so that's taken into consideration as well.

Cheers,
Tobi

Tara Conklin_esvt7l

Thanks, Tobi!
I appreciate the response. I've added my comment to the issue and am watching it. Hoping they don't deprecate the old macro until they fix this.

Laura Mehrkens

Hi @Tara Conklin could you share where you read that the legacy Jira issues macro will be deprecated by 2026?

Julia Ackermann

Hi @Laura Mehrkens,

will the legacy Jira issues macro actually be deprecated soon? I honestly hope it won't as we use it frequently in combination with the Table Transformer macro to display certain fields or merge tables. The new macro doesn't behave like a table so we would have to find a completely different solution.

Thanks for your response in advance and best regards

Welcome!

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

Quick Links

Find more posts tagged with

confluence

cloud

confluence-cloud

jira_issues_macro