Export, page history and email

Where the live table cannot run, the app builds a plain Confluence table from the same JQL and columns, as the person it is made for. This covers:

• 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

Only work items that person can see, with:

• Every column, with its display options.
• Up to 300 work items. A longer list ends with “Showing the first 300 of about 412 work items.” An empty result says “No work items match this JQL.”
• The JQL’s ORDER BY, never a reader’s sort.
• Full links to work items, projects and Assets objects.
• 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. A hidden one is its key and “(Not available)”.
• People as display names, progress as a percentage and rich text as plain paragraphs.

No icons, avatars or images. Dates use the export’s language and time zone, or UTC, marked UTC. Exports are read-only.

Limits

• 300 rows. For more, split the list over several macros with narrower JQL queries.
• About 20 seconds. Forge stops a function at 25, so a slow Jira can mean fewer rows. The closing line says how many.
• Lookups come last. If Assets fails, objects show their raw ids. If Work Item Selector fails, cells show linked keys and the reason.

When the table is left out

The macro never fails an export. Without a table, it writes one line and the page exports as usual:

Next

• Privacy and data handling
• Release notes