Jira wiki tab pdf#

The buttons underneath the table allow you to move to the next or previous page, or to the start or end of the list. If you are using JIRA 3.13 or later, the JIRA Issues macro will retrieve and show a 'page' of issues at a time. Can be indicated either as a percentage (%) or in pixels (px). The width of the table displaying the JIRA issues. If your JIRA server is version 3.13 or later, a value of 500 means that the JIRA Issues macro will return a maximum of 500 issues per page. If your JIRA server is version 3.12 or earlier, this means that the JIRA Issues macro will return a maximum of 500 issues. Note: If the URL in the 'url' parameter does not contain a tempMax argument, then the value of tempMax will default to 500. The URL of the XML view of your selected issues in JIRA Issue Navigator. This can help provide more context to the list of issues displayed. For instance, setting the title to 'Bugs-to-fix' will replace the default 'JIRA Issues' text. You can customise the title text at the top of the JIRA issues table with this parameter. Set the 'renderMode' parameter to 'static' if you want to disable the dynamic display features. View a page of issues at a time, for faster response times.Temporarily remove a column from the display.

Drag and drop the columns into a different order.Click the column headers to sort the output.

Jira wiki tab pdf#

The default is 'static' when the JIRA issues are displayed in a PDF or Word document, in an email message or in an RSS feed.īy default, the JIRA Issues macro offers a dynamic display with the following features: In formats not mentioned below, the default is 'dynamic'.

When the JIRA issues are displayed in a PDF or Word document, in an email message or in an RSS feed.

If you set the 'renderMode' parameter (see below) to 'static'.

Note that this height specification is ignored in the following situations: The height in pixels of the table displaying the JIRA issues. (The value 'false' also works and has the same effect as 'off'.) If the 'cache' parameter is set to 'off', the relevant part of the cache is cleared each time the macro is reloaded. The macro maintains a cache of the issues which result from the JIRA query. The count will be linked to your JIRA site. If this parameter is set to 'true', the issue list will show the number of issues in JIRA. See the JIRA documentation for a list of names. You can include any columns recognised by your JIRA site, including custom columns. Example columns are: key, summary, type, created, fixversion, updated, due, assignee, reporter, priority, status and resolution. This is useful when Confluence connects to JIRA with a different URL from the one used by other users.īy default, the following columns are shown:Ī list of JIRA column names, separated by semi-colons ( ). If you specify a 'baseurl', then the link in the header, pointing to your JIRA site, will use this base URL instead of the value of the 'url' parameter. By default, Confluence will show only the JIRA issues which the user is authorised to view. If this parameter is omitted or set to 'false', then the results depend on how your administrator has configured the communication between JIRA and Confluence. the issues which are visible to anonymous viewers, as determined by JIRA's viewing restrictions. If this parameter is set to 'true', JIRA will return only the issues which allow unrestricted viewing i.e.