Issue Summary

When exporting a page with the Legacy Jira issue Macro configured to show the results of a JQL search, the PDF shows a grey bar in place of the macro if the macro does not produce an error, but takes too long to actually get the results.

This is reproducible on Data Center: unknown

Steps to Reproduce

1. Set up or find a JQL query that when run in Jira advanced search takes more than 10 seconds to return results. One method to drive up the result wait time is to have the user be a member of hundreds of groups. The longer the JQL takes to resolve, the better. You should be able to get just shy of 30 seconds before Jira times out.

2. create a page with some content, and add in a Jira Legacy macro which searches for your slow JQL. Including the "fix version" and/or "affects version" fields can help ensure that the issue is reproduced. A query which returns at least 50 issues is also recommended to reproduce.

3. Export the page to PDF. If your query is slow enough, you should see that a grey bar is produced instead of the contents of the macro in your PDF. You may alternatively see an error like "failed to obtain the macro data".
You should also see a similar effect when editing the page.

Expected Results

The Jira issue macro is rendered in the PDF.

Actual Results

The PDF does not wait for the macro to complete loading before the PDF is rendered and downloaded resulting in either a grey bar, or an error to be rendered instead.

Workaround

It may be possible to work around the issue by reducing the time that it takes for the JQL to return. De-nesting any nested queries, reducing the number of groups that the exporting user is a member of, changing the fields that the Jira issue macro returns ("fix version" and/or "affects version" fields seem to be known offenders and can potentially be replaced by the "Build" field)