The problem
Existing JIRA Issues Macros do not show any data after upgrade to Confluence 5.2.3. Editing the page then resaving has no effect on the (${entries.size()} issues) text. Editing the macro itself and re-saving the page resolves the issue
Viewing the raw source without editing the jira macro looks like the code below:
<ac:macro ac:name="jiraissues">
<ac:parameter ac:name="title">5.7: BAU Release items</ac:parameter>
<ac:parameter ac:name="height">300</ac:parameter>
<ac:parameter ac:name="columns">Type;Key;Summary;Priority;Status;Assignee;QC Reference;External Reference</ac:parameter>
<ac:parameter ac:name="url">http: </ac:macro>
Editing and saving the page has no impact. However, editing the jira macro and then saving it (without actually changing it) it will then change the source to the following:
<ac:macro ac:name="jira">
<ac:parameter ac:name="columns">Type;Key;Summary;Priority;Status;Assignee;QC Reference;External Reference</ac:parameter>
<ac:parameter ac:name="server">ITSS JIRA</ac:parameter>
<ac:parameter ac:name="serverId">d3d13785-344a-3b8f-87be-7149ef11eca2</ac:parameter>
<ac:parameter ac:name="jqlQuery">project = Project AND fixVersion in ("5.7.0") AND labels in ("5.7-Release-Item") AND labels not in (ACL) ORDER BY key DESC</ac:parameter>
</ac:macro>
Note the change from using url to using jqlQuery
Workaround
- Upgrade JIRA Issues Macro to 5.0.2 if it is not yet at that version (Admin > Manage Add-ons)
- Edit the page with the macro on it
- Edit the macro (no need to change anything, just bring up the edit screen)
- Resave the page
NB: Be aware of CONF-30428 - if you currently have macros that reference filters, the macros will be decoupled from the filters and the JQL will be used instead.