Confluence 2.9 : JIRA Portlet Macro
This page last changed on Jul 27, 2008 by smaddox.
JIRA is the issue tracking and project management system supplied by Atlassian. The JIRA Portlet macro allows you to display a JIRA dashboard portlet on a Confluence page. To do this, you will need to include the URL of the portlet in the macro. JIRA Portlet Macro {jiraportlet:url=urlOfJIRAPortlet} On this page: Error formatting macro: toc: java.lang.NullPointerException
Displaying a JIRA Portlet on your Confluence PageHere's how you locate the URL of a JIRA portlet and put it into your JIRA Portlet macro:
Screenshot 1: Copy link location Parameters
ExampleBelow is an example of some macro markup code, requesting a portlet from the Atlassian public JIRA site: {jiraportlet:anonymous=true|url=http://jira.atlassian.com/secure/RunPortlet.jspa?portletKey=com.atlassian.jira.plugin.system.portlets:projectstats&description=Stats:%20Confluence%20(Versions)&projectid=10470&statistictype=fixfor&template=/portlets/dashboard/projectstats.jsp} Below are the results of the above macro markup, displayed on this Confluence page:
Displaying Issues which have Restricted Viewing
This section explains how to handle JIRA issues that have restricted viewing. Maybe your JIRA instance is not visible to anonymous visitors - everyone has to log in before they can see JIRA issues. Or maybe some of the JIRA issues are restricted to viewing by certain users only. Specifying Username and Password in the JIRA URL (Not Recommended)For Confluence 2.6.x and earlier, if your JIRA issues have restricted viewing (i.e. JIRA requires a login before allowing access to the issues), then you need to type a JIRA username and password into the macro markup code and save it onto the Confluence page. Append the following parameters to the end of the search URL: &os_username=MYNAME&os_password=MYPASSWORD where MYNAME is a JIRA username and MYPASSWORD is the corresponding password for that username. This username and password should not include an & symbol. Using Confluence-to-JIRA Trusted Communication (Recommended)For Confluence 2.7.0 and later, your administrator can set up trusted communication between Confluence and JIRA. The entire process is described in the Confluence Administrator's Guide. Here is a relevant extract from the above page: Setting Up Trusted Communication between JIRA and Confluence
The following options are available for determining the issues which will be retrieved from JIRA and displayed on the Confluence page:
TroubleshootingIdeas for new features or want more tips?If you have an idea for a new feature, please log it on our JIRA site. You will also find many hints and tips on our Confluence forum. Try asking a question or sharing your ideas with other Confluence users. Logging Bugs and Requesting SupportIf you have found a bug in this macro, please log it on our JIRA site. If you encounter a problem using this macro, please raise a ticket on our Support site. Known Limitations when used with JIRA CalendarIf you are using the JIRA Portlet macro in combination with the JIRA Calendar, paging will work only if your Confluence and JIRA sites are running on the same host. Otherwise, you see error messages like Access to restricted URI. Reason: the Calendar portlet communicates with JIRA via AJAX requests. Because of security concerns, browsers by default do not allow requests to any host different from the one the page was originally downloaded from. There is a workaround. If you wish, you can turn off this security check in your browser. The exact way depends on your browser version, so Google for hints.
RELATED TOPICSJIRA Issues Macro In the Administrator's Guide: Take me back to Confluence User Guide |
![]() |
Document generated by Confluence on Aug 07, 2008 19:09 |