-
Bug
-
Resolution: Fixed
-
High
-
5.2.3
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://url.com/sr/jira.issueviews:searchrequest-xml/27321/SearchRequest-27321.xml?tempMax=1000</ac:parameter> </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.
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page"){kind=icon}
[CONFSERVER-30429] Existing JIRA Issues Macros display (${entries.size()} issues) instead of issues after upgrading to 5.2.3
wendy64ca, using 5.0.3 should be enough to fix the problem. If it is not a case for you can you please create a support request and we will help you out (we would need some extra data from you to figure out why it is still a problem on your instance).
I'm testing migration from Confluence 4.3.7 (plugin v4.0.29) to Confluence 5.2.3 (which automatically upgrades to plugin v5.0.1). Upgrading to v5.0.3 of the plugin after migration does not solve this problem. How can I be sure that I won't still see it with Confluence 5.2.4, since it will have the same plugin version that I'm running now? Will something different happen during the upgrade? How does the old macro parameter format get converted to the new one?
The various problems with the JIRA issues macro are currently blocking our upgrade to Confluence 5.2. I really hope they're all going to be fixed soon. I actually experimented with staying at plugin v4.0.29 but that has some problems of its own, although they may be easier to live with.
Fixed in plugin version 5.0.2 which is available form marketplace and will be bundled with confluence v 5.2.4.
abm, I couldn't reproduce your issue with the icons. The icon urls should point directly to the jira instance the issues are retrieved from. Can you check the icons url (in the html page)? Is that url accessible from the browser? Would you mind creating a support request and we will help you out.
Upgrading to JIRA issues macro 5.0.2 to Confluence 5.2.3 solved this partly. Icons still missing. See https://jira.atlassian.com/browse/CONF-30384 for screenshots.
Arne Boye-Møller
added a comment - - edited Upgrading to JIRA issues macro 5.0.2 to Confluence 5.2.3 solved this partly. Icons still missing. See https://jira.atlassian.com/browse/CONF-30384 for screenshots.
Thanks Anatoli, I'll do that.