• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • 6.13.18, 7.8.1
    • 5.10.7, 6.0.3, 7.4.3
    • Macros - Jira Macros

      Summary

      There is an excessive delay in loading the editor for a Confluence page that has several Jira Issue Macros (JIM) that are using the 'Total Issue Count' option in the 'Display Options'. This appears to be linked to Jira servers/clusters that have a million issues (or more).

      Environment

      Confluence 7.4.3.
      Jira 8.5.8 (maybe other versions of JIRA as well)

      Steps to Reproduce

      1. Install Jira 8.5.8 and Confluence 7.4.3 in test environment. I used PSQL db for the test.
      2. Populate the application data in JIRA to have 500k to 1 million issues. Confluence can be at default settings.
      3. Setup an application link between the two servers.
      4. In Confluence, create a new test page with 15 JIM macros each using JQL to filter the table and make sure that in the 'Display Options' in the macro, the 'Total Issue Count' option is selected. The filter should have a high amount of issues included (500k to 1 million) among several of the macros. Save the page.
      5. Notice it reaches out to JIRA to pull total issues for each macro.
      6. While on the test page, click the EDIT button (top right).

      Expected Results

      The editor should load in a reasonably quick time, or at least inline with how long it takes to query and retrieve the total issue values from Jira.

      Actual Results

      The editor takes 3x-5x the time it should to fully load before being available to edit the page.

      Notes

      • The delay comes from the editor reaching out to JIRA and requesting/loading the total issue counts after the EDIT button has been pressed. This is to include the total issue count for the macros in the editor.
      • While viewing a page, there are asynchronous REST calls to get the total issue count for the macros (this is behaving normally) which is several times faster than in edit mode.
      • Customers have observed that the delay in v6.15.9 is 50% less than in v7.4.3. for the editor with the same dataset in Jira.

      Workaround

      • Splitting page into smaller pages will help with page load.
      • Starting from versions 7.8.1 and 6.13.18, in the dark features, we would need to add "confluence.extra.jira.edit.ignore.count" to prevent Confluence from making requests to Jira. Due to that change, instead of a real count number, we will see "x" in edit mode.

            [CONFSERVER-44664] Can not edit a page with 42 JIRA Issue Macros

            No work has yet been logged on this issue.

              qpham@atlassian.com Quan Pham
              lquiroga Ludo
              Affected customers:
              2 This affects my team
              Watchers:
              15 Start watching this issue

                Created:
                Updated:
                Resolved: