My workaround:

1.Open your Confluence page on Chrome

2.Click Ctrl+P or click print on your browser

3.Save your document as PDF. Gadgets will appear as expected.

Let me know if this works for u 

Hi, we are affected with this Bug on confluence V 7.4.7, can you open it? We are 2000 users on datacenter affected by this.

Thanks

I run into this many times and am always surprised how this functionality does not exist. It is so useful, and it makes our ability to communicate with our clients on wiki pages very hard

So I also rely on this feature to be able to export a status report to a PDF and send it easily.  But when you have filtered issue gadgets or structure in place, you get gibberish data. Please fix this.

I don't understand why this isn't on the roadmap. Why bother offering the export to pdf option in confluence? Most everything useful that needs to be shared is going to be in a gadget...I'll put my vote to reopen this issue.

This is a critical issue if you want for users to gain value out of using Confluence for a single source of information and sharing. Everybody needing the information doesn't have access (e.g. customers, partners, prospects, etc.) Therefore, creating documentation from Confluence, as I understood, was to be a core competency. The gadgets are part of Atlassian's solution and, instead of saying that it is complex to solve (although that seems to be the Atlassian's line on many issues and would indicate a different problem in design), Atlassian should go back and understand what their core competencies are develop ways to solve. Being hard doesn't mean it isn't of value and right to do.

This has become a critical issue as we are not able to share/distribute our executive level reports/summaries without additional work. Thus, begging the question of why we should utilize Confluence for this use case at all if we have to recreate the reports.

Creating a PDF of the webpage is not a good solution because you cannot control the content (e.g. URLS, headers, footers, etc.) like you can with the export > PDF. Therefore, the ONLY solution it to regenerate into a completely different document and creating screenshot of all the gadgets.

Dear Atlassian Product Manager,

I am using Confluence Wikis in my company for status reporting by various teams and then rolling it up in another page using excerpts, jira gadgets and page includes as required. I need the capability to export this to a word doc or a pdf so that the Jira hyperlinks in the report also work. Currently, gadgets, page includes do not render properly. I am evangelizing Jira and Confluence in my company here in Silicon Valley, and need this export capability for creating docs from wikis, sending reports to senior management, or else our evaluation will not be approved and we may have to switch back to media wiki or something else. It has been almost 4 years since the original issue was reported, so can you reconsider and open this issue? It is much appreciated. Thanks.

Uma

We have the same Problem. I would recommend reopening this issue.

The workaround works fine until you won't make changes in the PDF layout information of pages in the space settings.
I think its sad to offer the pdf-export-functionality even though it doesn't works fine

We've had a similar problem, instead of using the export to PDF function in Confluence, try clicking print and printing it to PDF. If you are using Chrome that feature should be built in, not sure about other browsers but there is some free software that will do this (Prime PDF is one of them).

We are having a similar problem with using the filter-results-gadget.
When we try to export a Confluence-page with the filter-results-gadget (getting the content from Jira) into a PDF-file, the result is not readable. The content displayed in Confluence is what it is supposed to look like, but the PDF-content looks like this:
<a
href="https://[Confluence-service-adress]/plugins/servlet/gadgets/ifr?container=atlassian&mid=1013668315136&country=DE&la
ng=de&view=default&view-params=%7B%22writable%22%3A%22false%22%7D&st=atlassian%3AvW%2FNnVMV9dw9sRI7D
4KhjoJmLqA0Ck%2F8yCJGiryindBj9c9AUSMWxVgMkPZsxx7glcEQg2FLc1wana6D4jw9Wh75aYFJJ9yTF7uXvNgUDu338ebTkhl4J9Wdj4mk
E21rIyb4%2FuD4UDq%2BRR9KrxoskAwevXsUyZNXdVWqYMjG69JAdh%2BgDdzDmTqEILwZIqi2X%2F4PQoulhXKtDP1rAtzWmVndKtlsYsg
Modo4y4zL2L3gb6AE%2Be%2FcqizHR5M3m4c9sNZzblX69QWVJtUfkdtG%2BYuLjK889V%2FOneE%2B%2F15dECZHER0HljyRrw1G0RKI
Xqh6dvLCKfbhlM%2FI1QZDWIFR%2Btx6pno%3D&up_filterId=filter-15184&up_num=50&up_isConfigured=true&up_isPo
pup=false&up_columnNames=issuetype%7Cissuekey%7Csummary%7Ccustomfield_10746%7Ccustomfield_10745&up_refresh=fal
se&url=https%3A%2F%2F[JIRA-service-adress]%2Frest%2Fgadgets%2F1.0%2Fg%2Fcom.atlassian.jira.gadgets%3Afilter-results-gadget%2Fg
adgets%2Ffilter-results-gadget.xml&libs=auth-refresh#rpctoken=1076036999">Filterergebnisse</a>

The workarounds are still working but they are not really useful to us.
Please reopen this ticket an solve it.

This would be great for reporting. Workarounds are a kind of solution but from the other hand are quite amateur solutions comparing to other confluence functionalities.

Marking this as close, won't fix. Please see the Atlassian status for the reason why.

This is a very critical piece of functionality for us that is broken how soon can we expect a fix for this?

We want to use Confluence for writing our documentation.
The documentation should contain a page with a knowledgebase. The knowlegebase is handled as a issue-type in JIRA. To display the knowledgebase in Confluence we want to use the Jira Filter Results gadget.