Export to Word does not export content of expand macro

[Wendy Pangilinan]

I have organized my cloud pages with multiple expands within each page. When I export the page to either a Word doc or PDF, the contents of the expands does not export. I have tried expanding each macro to reveal the contents, and then exporting them. This does not solve the problem. The downloaded file still only shows a closed expand with the title. How can I get the contents of the pages to export in their entirety?

[Aron Gombas _Midori_]

I know that the Scroll Word Exporter app overcomes several limitation of the built-in Word export feature. If I were you, I would try if it works better with expandables, too.

[Mattia _Communardo_]

Hello @Wendy Pangilinan

Welcome to the community.

The issue of macro content not always exporting to PDF or Word is acknowledged by Atlassian. Here is the item that you can watch and vote on. https://jira.atlassian.com/browse/CONFCLOUD-81113.

Kind regards,
Mattia

[David Nickell]

I attempted a test export to word with an expand that contained t text -- and it expanded as expected.   I guess the next question is what is within your expands?

[Wendy Pangilinan]

Thank you for doing that David. I have tables with text and screenshots in my expands.

[David Nickell]

You are welcome - the next test was pretty simple -- I added a table with a few columns and rows, then inserted some text and pictures.  No problems.

Then I added a Jira table of work items -- that DID NOT export.

MORE INFO  (From ChatGPT)

Why issues sometimes disappear in the export

• The Jira macro does not always include full detail in exports. Instead, it often flattens to a static table snapshot. If the macro is configured with dynamic filtering or paging (e.g., “show 20 issues”), the export might only show what’s currently rendered.

• Some Jira macros are JavaScript-based renderings in the browser. Those don’t carry over into Word/PDF exports, so the result may be blank or truncated.

• Attachments, comments, or “expandable” details from Jira macros almost never survive the export — only top-level fields like key, summary, assignee, status.

What to check

• In Confluence, click Edit Page → find your Jira macro → look at its Display Options. Try setting it to a static table of fields (e.g., Key, Summary, Status). That exports more reliably than “Total Issue Count” or “Two-Dimensional” views.

• Try Word vs PDF export — sometimes one format captures more than the other.