Documentation for Confluence 2.5.4 - 2.5.8.
Documentation for [Confluence Cloud] and the latest Confluence Server is available too.

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:

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?:

(tick)

Setup Notes

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

As a result of RSS feed improvements, the (outdated) JIRA Issues Macro differs between JIRA 3.6 and 3.7.

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

(tick)

None

Older than 2.2.10

3.7

(error)

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

Older than 2.2.10

Older than 3.7

(tick)

None

Using The JIRA Issues Macro

See the User Guide entry.

JIRA Issue Parameters

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:

{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:

type key summary

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Troubleshooting

Unable to render {include} The included page could not be found.
  • No labels