Baselines All documentation pages
Jira issue macros
If your Confluence pages embed Jira issues or filters, those macros come out of a PDF export with their issue key, summary and status on them, not as an empty placeholder.
How it works
When you export a version to PDF, Baselines asks Confluence to render each page that carries a Jira issue or filter macro, as Confluence renders it for a reader, and puts that in the document. The Jira data comes through your site’s own Jira connection, the one an administrator already set up in Confluence.
There is no Jira settings screen and Baselines never asks for a Jira account, password or API token. If your site’s application link to Jira works for readers, it works for exports. Pages with no Jira macros are exported normally.
In Compare
Confluence renders a Jira issues macro with today’s data for both versions of a page, so Compare does not compare its output and says so on the page.
Notes
- Pages with Jira issues macros print today’s data, and each is marked so in the PDF: the issue data reflects the issues at export time, not at the version’s as of date.
- An issue that the person exporting cannot see in Jira does not appear: the macro renders for them the way Confluence would render it for them.
- Everything is assembled into the single exported PDF, so it stays readable offline.
Was this page helpful? Yes · No · Contact support