Skip to content

Comment Macro

The Comment Macro displays the comments of the connected Jira work item directly on the Confluence page. Comments are rendered as a thread that visually matches Jira’s native comment UI: avatar, author, relative timestamp, an (edited) marker, and the formatted comment body (headings, lists, mentions). Replies are nested below their parent comment.

The macro is display-only: it shows comments but does not allow posting, editing, or reacting to them.


  • Border — Enable or disable the border around each top-level comment (with its replies). Enabled by default.
  • Comments per page — Number of top-level comments shown per page: 5, 10, 20, or 50. Default: 10. Replies always stay together with their parent comment and are not counted separately.

When the work item has more top-level comments than the configured page size, the macro shows a pagination control below the thread. The control is hidden when everything fits on a single page.

Macros configured before pagination existed have no Comments per page value stored. They render with the default of 10 comments per page, and the configuration dialog shows 10 as the selected value.


Only external comments are displayed. A comment is treated as internal — and hidden — when either of the following applies:

  • It is a Jira Service Management agent-only comment (jsdPublic is false).
  • It has a visibility restriction set (a role or group can see it).

All other comments — including JSM comments marked public and non-JSM comments — are shown.


If the connected work item has no comments, the macro shows the message “No comments yet.” instead of an empty thread.


Like all AutoPage macros, the Comment Macro requires Jira product access: a Confluence user without a Jira licence cannot load the comments. Comment content is fetched using the viewing user’s own Jira permissions, so a user who cannot open the work item in Jira also does not see its comments.


The Comment Macro does not offer a Sync Mode setting. Comments are always retrieved live when the Confluence page is loaded, so the thread always reflects the current state of the work item. As with the “Live Update” mode of the other macros, no comments are displayed if communication with the Jira API fails.