Status: Closed (View Workflow)
6.1.1, 6.1.4, 6.2.4, 6.6.1, 6.13.6
Confluence 6.1.1 and Jira 7.3.3, both on the same server
No proxy or SSL configured
OAuth with impersonation
Custom field created as:
Name: Business Impact
Type: Select List (single choice)
Available Context(s): Issue type(s): Global (all issues)
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.
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
Macros render correctly in all cases.
Macros fail when there's a custom field on them.
Upgrade to Confluence 7.7.4 or above, which contains a performance fix for Jira Issues Macro. This is detailed under
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.
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.
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.