Attachments Macro
The Attachments Macro displays the attachments of the connected Jira work item directly on the Confluence page. You can choose between a list or table layout and select which attachment fields to show.
The macro only displays the attachments — it does not copy them. The files remain in Jira, and no Confluence page attachments are created when the rule runs. As a result, the list always reflects the attachments currently present on the work item.
Configuration
Section titled “Configuration”- Layout — Choose between List or Table display.
- Display Fields — Select which fields are shown for each attachment (see below).
- Sort By — Select the order in which the attachments are listed (see below).
Display Fields
Section titled “Display Fields”| Field | Shows |
|---|---|
| File Name | The name of the attached file, linked to the file in Jira. |
| Size | The file size of the attachment, for example 1.05 MB. |
| Type | The file type in readable form, for example PDF or Image. |
| Uploaded | The date and time the attachment was added to the work item. |
| Uploader | The user who added the attachment. |
| Preview | A generic file icon in front of the entry, identical for all file types. |
Sort By
Section titled “Sort By”| Option | Orders attachments by |
|---|---|
| Date (Newest First) | Upload date, most recent first — default |
| Date (Oldest First) | Upload date, oldest first |
| Name (A-Z) | File name, ascending |
| Name (Z-A) | File name, descending |
| Size (Largest First) | File size, largest first |
| Size (Smallest First) | File size, smallest first |
When the work item has no attachments
Section titled “When the work item has no attachments”If the connected work item has no attachments, the macro still renders: an empty table including its header row. It does not disappear from the page and does not report an error.
Limits
Section titled “Limits”All attachments of the work item are displayed. There is no maximum number of entries, no pagination or truncation, and no exclusion by file size or file type.
Downloading attachments
Section titled “Downloading attachments”The displayed file names are links to the attachment in Jira. Clicking an entry downloads the file.
Downloads are resolved with the individual user’s own Jira permissions. This is the key difference from the metadata: the attachment list itself ignores Jira project permissions, but the file behind it does not.
| User | Sees the attachment list | Can download the file |
|---|---|---|
| No Jira product access (no licence) | No — an error message is displayed instead | No |
| Jira licence, but no access to the work item | Yes, including all file names | No |
| Jira licence with access to the work item | Yes | Yes |
Permissions and visibility
Section titled “Permissions and visibility”Like all AutoPage macros, the Attachments Macro requires Jira product access: a Confluence user without a Jira licence does not see the attachment list. For licensed users, the macro does not evaluate Jira project or issue permissions, so the attachment list is rendered even if that user could not open the work item in Jira.
Sync behaviour
Section titled “Sync behaviour”The Attachments Macro does not offer a Sync Mode setting. The attachment list is always retrieved live when the Confluence page is loaded, so it always reflects the current state of the work item. As with the “Live Update” mode of the other macros, no attachment data is displayed if communication with the Jira API fails.
Troubleshooting
Section titled “Troubleshooting”Runtime exited with error: exit status 7
Section titled “Runtime exited with error: exit status 7”Error message:
AutoPage - Attachments • RequestId: <request-id> Error: Runtime exited with error: exit status 7This message is displayed in place of the attachment list for users without Jira product access. The macro cannot retrieve the attachments because the viewing user has no Jira licence.
Resolution: Assign Jira product access to the user, or restrict the Confluence page to users who have it. Note that the message is technical rather than descriptive — users reporting a “broken macro” with this text are usually missing a Jira licence.