This is not an issue for users running the latest versions of Confluence and JIRA. However, users using Confluence versions older than 2.2.10 to access JIRA 3.7 must upgrade Confluence or patch the JIRA issues macro to handle the 3.7 format.
Confluence
JIRA
OK
Action Required
2.2.10, 2.3
Any version
None
Older than 2.2.10
3.7
Stop Confluence, open your Confluence install directory and remove the file \WEB-INF\lib\jira3.jar. Download the JIRA 3.7 version and rename it to jira3.jar
The following parameters can be embedded in the macro call.
Parameter
Required
Default
Description
url
yes
none
The URL of the XML view of your selected issues in Jira Issue Navigator.
columns
no
none
a semi-colon delimited list of jira column names. Valid columns are key, summary, type, created, updated, due, assignee, reporter, priority, status and resolution
count
no
false
true will output the number of issues in JIRA, linking the count to the JIRA instance
cache
no
on
'off' will refresh the jiraissues cache, forcing a reload on the page before the display
baseurl
no
the header link to the issue navigator will use this base url (used when Confluence connects to Jira with a different URL to normal users)
tempMax
no
20
limits the number of results you get back. This is the case even when count is set to true.
Example
This macro call requests a filter results from the Atlassian public JIRA instance:
For problems relating to the JIRA Issues Macro, click on your query below for the solution.
Issues Appear Out Of Date Using cache with this macro it can be that you have stale data in you table. You can force a refresh of the table by clicking the Refresh button in the top-right hand corner of the table.
'Error Rendering Macro' or No Issues Are Displayed or Not All Issues Are Displayed You must append a JIRA username and password to your JIRA issues filter URL. That JIRA user must also have permission to view the all issues returned by the filter, otherwise they will be omitted. Please append the os_username and os_password as described below so that jiraissues:url=http://host.com/secure/IssueNavigator.jspa?... becomes jiraissues:url=http://host.com/secure/IssueNavigator.jspa?...&os_username=MYUSERNAME&os_password=MYPASSWORD where MYUSERNAME and MYPASSWORD are a JIRA login.
'Error rendering macro: java.io.IOException: Could not download' You may need to configure Confluence to acknowledge your proxy server before it is able to download the feed.
'Error rendering macro: java.io.IOException: Error on line -1: Premature end of file' Did you select an existing JIRA filter? If you did, your issues filter URL will end with .../12345/SearchRequest-12345.xml where 12345 is any number. You should retry using a new and unsaved filter.