Uploaded image for project: 'Confluence Server and Data Center'
  1. Confluence Server and Data Center
  2. CONFSERVER-53500

JIRA Issues macro fails with custom field

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Low
    • Resolution: Fixed
    • 6.1.1, 6.1.4, 6.2.4, 6.6.1, 6.13.6
    • 7.7.4, 7.4.7
    • Macros - Jira Macros

    Description

      JIRA macro does not load when a Custom Field is added as a Column to Display. After saving the page, the macro shows up as "loading issues" with a spinning wheel. When it finally fails, the error message can be seen as in the screenshot, and the macro is greyed out.

      How to replicate

      Created blank page on brand new Confluence instance, added one JIRA Issues macro containing a custom field (A) and another without the custom field (B) - Macros break
      Edited macro A in order to remove the custom field - Macros break
      Removed macro A and inserted another macro without the custom field (C) - Macros render properly
      Edited macro B in order to add the custom field - Macros break

      Expected results

      Macros render correctly in all cases.

      Actual results

      Macros fail when there's a custom field on them.

      Recommended Resolution

      Upgrade to Confluence 7.7.4 or above, which contains a performance fix for Jira Issues Macro. This is detailed under CONFSERVER-56017.

      Note that an initial attempt to fix the performance issue was made in Confluence versions 7.4.1 and 7.5.0. However, it caused other problems and was reverted in Confluence 7.4.3 and 7.6.2. A proper fix was introduced in Confluence 7.7.4.

      19 Oct 2020 Update - For customers who would prefer to stay on long term support versions such as 7.4.x, Atlassian is currently looking into backporting the above fix to existing LTS release streams, so stay tuned.

      Workarounds

      Workaround - Increase Jira timeout (Confluence 7.4.1+)

      Set the system property confluence.jira.connection.timeout to a value higher than the default of 30000 (30 seconds)
      This will increase the connection timeout for Confluence to fetch the results of a query from Jira.

      Workaround - Clean up Jira custom fields (all versions)

      When Jira has a large number of custom fields, it can cause performance problems. Cleaning up the custom fields that aren't used can improve performance.

      Workaround - Use Jira Filter Results Gadget instead (all versions)

      If you are unable to upgrade, the Jira Filter Results Gadget can be added to Confluence via Registering External Gadgets to load custom fields.

      Attachments

        Issue Links

          Activity

            People

              qpham@atlassian.com Quan Pham
              csantos@atlassian.com Camila Santos
              Votes:
              39 Vote for this issue
              Watchers:
              65 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: