Skip to content
ENETDocumentation is only available in English.
Marketplace (opens in a new tab)

Export, page history and email

The interactive table cannot run inside a PDF, a Word file, an old page version or an email. For those, Confluence asks the app for the list instead, and the app answers with an ordinary Confluence table built from the same JQL query and columns.

This happens for:

  • Export to PDF and Export to Word from the page, and PDF exports of a whole space
  • Page history, when an earlier version of the page is viewed
  • Notification emails that include the page’s content

What the table contains

The export runs as the user Confluence renders the page for, so it contains only the work items that person can see in Jira, like the table on screen.

  • Every column, with its display options.
  • Up to 300 work items, whatever the page size. A longer list ends with a line such as “Showing the first 300 of about 412 work items.”
  • Links to work items, projects and Assets objects, as full addresses that work outside Confluence.
  • Statuses as Confluence status lozenges: green for done, blue for in progress, grey otherwise.
  • Assets objects as the label, linked, and the key.
  • Work Item Selector fields as one line per work item: the key, linked, then the card’s fields joined with “ · “.
  • People as display names, progress as a percentage and rich text as plain paragraphs.

Exports show no icons, avatars or images of any kind.

Dates are written as on screen, in the language and time zone Confluence passes with the export. When it passes no time zone, times are in UTC and marked UTC. A relative date is worked out when the export is made.

The export is read-only in both editions.

Limits

  • 300 rows. For more, split the list over several macros with narrower JQL queries.
  • About 20 seconds. Atlassian Forge stops an app function after 25 seconds, so the export stops fetching rows at 20. A slow Jira can mean fewer than 300 rows; the closing line then says how many are shown.
  • Assets and Work Item Selector lookups come after the rows. If one fails or runs out of time, the table still exports: Assets cells show each object’s key, or its id, and Work Item Selector cells show the work item keys, linked.

When the table is left out

The export never fails because of the macro. When it cannot build the table, it writes one line in its place and the rest of the page exports as usual:

Line in the export Cause
Work item list not included in this export: the macro is not configured. The macro has no JQL query or columns yet.
Work item list not included in this export: the app license is inactive. The subscription has lapsed.
Work item list not included in this export: followed by Jira’s reason Jira rejected the JQL, or could not be reached.

Checking an export problem

The export runs on Atlassian Forge, not in the browser, so it leaves nothing in the browser’s console. When you write to support, name the page, the kind of export and roughly when it ran.

Next