External Content

Ways to include, summarise or refer to content from other servers.

Notation Comment
{rss:url=http://host.com/rss.xml}

{rss:url=http://host.com/rss.xml|max=5}

{rss:url=http://host.com/rss.xml|showTitlesOnly=true}

Display the contents of a remote RSS feed within the page. Note: feeds are cached for 60 minutes before being retrieved again.

The 'max' parameter can be used to limit the number of entries displayed.

Example:

Sample RSS Feed (RSS 2.0)
(Feed description here...)
My Item ( Dec 30, 2003 06:53)
And part of the item content here...
Another Item ( Dec 30, 2003 06:53)
And part of the item content here...

You can specify 'showTitlesOnly=true' to show only the RSS feed titles. This parameter defaults to false.

You can specify 'titleBar=false' to hide the feeds titlebar. This parameter defaults to true.

{jiraissues:url=http://jira.rss.url}

{jiraissues:url=http://jira.rss.url|
columns=type;key;summary}

{jiraissues:url=http://jira.rss.url|
count=true}

{jiraissues:url=http://jira.rss.url|
cache=off}

{jiraissues:url=http://jira.rss.url?
os_username=johnsmith&os_password=secret}

{jiraissues:url=http://jira.rss.url|
anonymous=true}
Imports and displays JIRA issue list RSS as inline content for the page. You can easily customize the list and order of the columns being displayed, by specifying columns parameter.

Not specifying columns will lead into the default column list and order.

Allowed columns are: key, summary, type, created, updated, assignee, reporter, priority, status, resolution.

Specifying count=true will cause the macro to just print out how many issues were in the list, without printing the list.

Using count=true will cause the macro to just print out how many issues were in the list, without printing the list.

Using cache=off will force the macro to refresh its internal cache of Jira issues.

Note: Certain filters may require a logged-in user in order to work. If a trust association has been established between Confluence and JIRA, user authentication details will be passed between the servers automatically. This functionality requires JIRA 3.12 or later. If a trust association is not available you can send the required login by appending:
&os_username=yourJiraUsername&os_password=yourJiraPassword
to the end of your jira issues URL.

You can prevent the jiraissues macro from attempting to use a trusted application link by specifying anonymous=true. Issues will then be retrieved anonymously.

Example:

Atlassian JIRA (This file is an XML representation of some issues)
Key Summary Assignee Status Res Updated
TEST-100 Add JIRA support John Gordon Open UNRESOLVED 01/Jan/04
TEST-103 Add JUnit Support Robert Matson In Progress UNRESOLVED 25/Dec/03
TEST-108 Add RSS Support Bill Watson In Progress UNRESOLVED 23/Dec/03
TEST-109 Add Search Support Fred Morit Closed FIXED 03/Jan/04

{jiraportlet:url=http://jira.portlet.url} Imports and displays JIRA 3 portlet into a Confluence page.

You can get the URL for the portlet by configuring the portlet into your JIRA dashboard. While in configuration mode, you can copy the portlet URL from the top of the portlet display.

Note: Certain filters may require a logged-in user in order to work. Hence you may need to append:
&os_username=yourJiraUsername&os_password=yourJiraPassword
to the end of your portlet url.

{junitreport:directory=file:///c:/test-reports}
(currently only picks up result files in XML format. Set ant formatter to "xml")

{junitreport:url=file:///test-reports/TestRep.xml}
Displays the results of a series (or single) JUnit test.

Success Rate Tests Failures Time(s) Time(s)
93%
14 1 0 1.531

{google-calendar}
http://www.google.com/calendar/feeds/rAndOmleTT3r5g0h3r3@group.calendar.google.com/public/basic http://www.google.com/calendar/ical/m0r3raNd0ml3tTer5@group.calendar.google.com/public/basic.ics {google-calendar}

Displays the specified Google Calendars in Confluence. Any of the standard Google calendar links (XML, ICAL, HTML) will work. You can have multiple calendars listed, one per line. You can also comment lines out by prefixing them with '//'.

Parameters

  • mode - The mode the calendar is in. Either 'month', 'agenda' or 'mini'. Defaults to 'month'.
  • controls - The controls to show. Either 'all' (which displays the Google logo and the title), 'navigation' (which displays just the navigation bar) or 'none'. Defaults to 'navigation'.
  • title - The title to display. Only visible when controls is set to 'all'. Defaults to the name of the calendar.
  • eventsPerDay - The minimum number of events to give space to in 'month' mode. Defaults to 5.
  • width - The width of the calendar in either pixels ('500' - no 'px') or percentage ('100%'). Defaults to 100%
  • height - The height of the calendar in pixels ('600' - no 'px'). Defaults to '610'.
  • bgcolor - The background color of the calendar. Defaults to '#FFFFFF'.
  • firstDay - The first day of the week. Eg. 'Monday'. Defaults to 'Sunday'.
  • colors - A comma-separated list of colors for events, listed in the same order the calendars appear in the macro body. Colors may be standard names ('red', 'blue', etc) or '#'d values (eg. '#FFFFFF', 'AD3E8B', etc). This currenly only applies in 'mini' mode.
{im:myscreenname|service=AIM}
{im:me@hotmail.com|service=MSN|showid=false}

Displays a graphic indication of whether an IM user is online. You must supply a valid user ID as the default argument and the desired service.

Parameters

  • (default) - The user id/screen name.
  • service - The name of the service to check. May be 'aim', 'gtalk', 'icq', 'msn', 'sametime', 'skype', 'wildfire' or 'yahoo'.
  • showId - (optional) If 'false', the user's id will not be shown.