How to remove blank space on PDF export with Jira results

Ilia Fonariov February 6, 2020

When exporting a page to PDF that contains multiple Jira results, if for example the secondary Jira result has a long list of issues - on the PDF the issues list will display on a next page leaving a lot of empty space on the previous page.

Is it possible to remove this empty space and have the issue list just cut off on the first page and continue on the next?

Screenshot below

issue_results_pdf.png

issue_results_pdf.png

1 answer

0 votes
Shannon S
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 18, 2020

Hello Ilia,

Thank you for bringing this to us.

From my understanding, you have a large gap of space between each Jira issues macro on a PDF export. Is that right?

Does this occur both with a single page export and a space export? If you want to test, you can do a space export of just that one page in Confluence by unchecking the other pages.

Lastly, can you let me know what your Confluence version is, and if you have any custom PDF CSS script added?

Thank you!

Shannon

Ilia Fonariov February 20, 2020

Hi Shannon,

Yes the PDF generates a large empty space beneath a Jira Macro IF the results of the NEXT Jira Macro are too long to fit in the remaining area.

If we have a Jira macro that starts off at the top of the page and would be longer than one page, it would break it at the end of the page and continue on the next one (expected behaviour).

The issue was observed on single Confluence page export as we have no need to export the space at this time.

At the time the question was posted it was observer on Server version 7.2.1, and later again on 7.3.1 - no custom CSS was applied..

Since then however, we played around with the PDF stylesheets to fit the information as we desire.

Shannon S
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 10, 2020

Hi Ilia,

Thank you for confirming that. Was there a certain amount of data in the Jira issues macro that you noticed was causing this?

Can you share with us the fix you ended up applying to correct the issue?

Thank you!

Shannon

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events