Usage:
{jiraissues:url=jira_rss_url|columns=columns}
Description:
Display a list of JIRA issues in a page. |
Input:
See parameters table below.
Output:
Nice looking list of issues in a Confluence page
Bundled with Confluence?:
|
This page is outdated. Please see new page. |
You can embed a JIRA issue into your Confluence page. This page covers parameters available when calling the macro.
Usage: |
{jiraissues:url=jira_rss_url|columns=columns} |
|
Description: |
|
|
Input: |
See parameters table below. |
|
Output: |
Nice looking list of issues in a Confluence page |
|
Bundled with Confluence?: |
|
1. HTTPS
The JIRA issues macro can access a JIRA instance running under SSL as long as the Confluence server is set to accept the JIRA SSL certificate.
2. JIRA 3.7 Link Format Change
See the User Guide entry.
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. |
This macro call requests a filter results from the Atlassian public JIRA instance:
{jiraissues:url=http://jira.atlassian.com/secure/IssueNavigator.jspa?view=rss&pid=10470&fixfor=10650&sorter/field=issuekey&sorter/order=DESC&tempMax=25&reset=true|columns=type;key;summary}
|
The filter results are embedded in the page as:
