NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.

      The new JIRA issues macro released to customers does not asynchronously load JIRA issues. As a result, some pages can timeout with lots of issues.

      More description from the related issue :
      Page load times tend to increase exponentially when multiple JIRA issues macros are used, even for simple queries.

      As a workaround you can limit the amount of issues returned or use dynamic render mode which appears to use caching better, but it could be improved for both modes.

      To reproduce:

      1. Create a page
      2. Add a JIRA issues macro with this XML view: https://jira.atlassian.com/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?jqlQuery=project+%3D+CONF+AND+issuetype+in+%28Bug%2C+%22New+Feature%22%2C+Improvement%29+AND+fixVersion+%3D+%224.2.2%22+AND+status+in+%28Resolved%2C+Closed%29+ORDER+BY+priority+DESC%2C+key+DESC&tempMax=200
      3. Save the page and monitor page load time
      4. Edit the page and add copy/paste the JIRA issues macro to create multiples
      5. Save the page and monitor page load time

      Page will load times will increase exponentially, even if the same query is being returned by each macro.

            [CONFSERVER-30115] JIRA issues macro times out pages with lots of issues

            Tbricks AB added a comment -

            Jira macros which are posted under comments are extremely slow with page load times of 10 to 20 seconds for large number of Jira cases.
            Also sometimes still receive errors for failing to load macro. This is under Confluence 5.6.4, see CONF-35655 for slow load times.

            Tbricks AB added a comment - Jira macros which are posted under comments are extremely slow with page load times of 10 to 20 seconds for large number of Jira cases. Also sometimes still receive errors for failing to load macro. This is under Confluence 5.6.4, see CONF-35655 for slow load times.

            Hi there,
            This seems to still repro on our 5.4.4.
            Is there something we have to do on our side to make this go away?

            Deleted Account (Inactive) added a comment - Hi there, This seems to still repro on our 5.4.4. Is there something we have to do on our side to make this go away?

            Hi obrush You can read more about the problem in the linked duplicate issue : https://jira.atlassian.com/browse/CONF-25835. I hope this helps!

            Ruchi Tandon added a comment - Hi obrush You can read more about the problem in the linked duplicate issue : https://jira.atlassian.com/browse/CONF-25835 . I hope this helps!

            Hi,

            Could you please explain the way of resolution of this issue for the masses?
            How can I access to extranet.atlassian.com to read the details?

            Oleksiy Brushkovskyy added a comment - Hi, Could you please explain the way of resolution of this issue for the masses? How can I access to extranet.atlassian.com to read the details?

              ndang Nguyen Dang
              smansour Sherif Mansour
              Affected customers:
              7 This affects my team
              Watchers:
              18 Start watching this issue

                Created:
                Updated:
                Resolved: