This page last changed on Jan 04, 2007 by david.soul@atlassian.com.
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.
Cannot Access Issues When JIRA Uses HTTPS
Check out Troubleshooting HTTPS or SSL-related Problems.
'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.
Issue icons are not displayed
Check that you are using the correct macro version for JIRA.
|