-
Bug
-
Resolution: Fixed
-
High
-
5.2-OD-5
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:
- Create a page
- 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
- Save the page and monitor page load time
- Edit the page and add copy/paste the JIRA issues macro to create multiples
- 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.
- is duplicated by
-
CONFSERVER-25835 Improve performance/caching of multiple JIRA Issues macros
- Closed
- relates to
-
CONFCLOUD-30115 JIRA issues macro times out pages with lots of issues
-
- Closed
-
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
Wiki Page Loading...
-
Wiki Page Loading...
[CONFSERVER-30115] JIRA issues macro times out pages with lots of issues
Workflow | Original: JAC Bug Workflow v3 [ 2893405 ] | New: CONFSERVER Bug Workflow v4 [ 2985348 ] |
Workflow | Original: JAC Bug Workflow v2 [ 2793116 ] | New: JAC Bug Workflow v3 [ 2893405 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JAC Bug Workflow [ 2722898 ] | New: JAC Bug Workflow v2 [ 2793116 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2392921 ] | New: JAC Bug Workflow [ 2722898 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 [ 2276099 ] | New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2392921 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5.1 - TEMP [ 2234690 ] | New: Confluence Workflow - Public Facing - Restricted v5 [ 2276099 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2197391 ] | New: Confluence Workflow - Public Facing - Restricted v5.1 - TEMP [ 2234690 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 [ 1934019 ] | New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2197391 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v3 [ 1736116 ] | New: Confluence Workflow - Public Facing - Restricted v5 [ 1934019 ] |
Description |
Original:
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: # Create a page # 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 # Save the page and monitor page load time # Edit the page and add copy/paste the JIRA issues macro to create multiples # 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. |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This bug report is for *Confluence Server*. Using *Confluence Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/CONFCLOUD-30115]. {panel} 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: # Create a page # 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 # Save the page and monitor page load time # Edit the page and add copy/paste the JIRA issues macro to create multiples # 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. |