Comments
Comments
Section titled “Comments”Manage Confluence page comments - footer comments, inline comments, replies, and resolution.
Prerequisites
Section titled “Prerequisites”- Authenticated profile (
atlcli auth login) - Space permission: View to list comments, Edit to add/modify comments
Overview
Section titled “Overview”Confluence supports two types of comments:
- Footer comments - Appear at the bottom of the page
- Inline comments - Attached to specific text selections
atlcli fully supports both types with CRUD operations.
Footer Comments
Section titled “Footer Comments”List Comments
Section titled “List Comments”atlcli wiki page comments list --id 12345Options:
| Flag | Description |
|---|---|
--id | Page ID (required) |
--json | JSON output |
Add Comment
Section titled “Add Comment”# Using positional argumentatlcli wiki page comments add --id 12345 "Great documentation!"
# From a fileatlcli wiki page comments add --id 12345 --file ./comment.txtOptions:
| Flag | Description |
|---|---|
--id | Page ID (required) |
--file | Read comment text from file |
Reply to Comment
Section titled “Reply to Comment”atlcli wiki page comments reply --id 12345 --parent 67890 "Thanks for the feedback!"Options:
| Flag | Description |
|---|---|
--id | Page ID |
--parent | Parent comment ID to reply to |
--file | Read reply text from file |
Inline Comments
Section titled “Inline Comments”Inline comments are attached to specific text in the page content.
List Inline Comments
Section titled “List Inline Comments”atlcli wiki page comments list --id 12345 --inlineAdd Inline Comment
Section titled “Add Inline Comment”# Match text in page and attach commentatlcli wiki page comments add-inline --id 12345 --selection "text to match" "Consider rewording this"
# If text appears multiple times, use --match-indexatlcli wiki page comments add-inline --id 12345 --selection "common phrase" --match-index 2 "Comment on third occurrence"Options:
| Flag | Description |
|---|---|
--id | Page ID |
--selection | Text string to match in page content |
--match-index | Which occurrence to match (0-indexed, default: 0) |
--file | Read comment text from file |
Comment Resolution
Section titled “Comment Resolution”Mark comments as resolved (for review workflows):
# Resolve a footer commentatlcli wiki page comments resolve --comment 67890
# Resolve an inline comment (specify type)atlcli wiki page comments resolve --comment 67890 --type inline
# Reopen a resolved commentatlcli wiki page comments reopen --comment 67890Options:
| Flag | Description |
|---|---|
--comment | Comment ID |
--type | Comment type: footer (default), inline |
Delete Comment
Section titled “Delete Comment”# Delete footer commentatlcli wiki page comments delete --comment 67890 --confirm
# Delete inline commentatlcli wiki page comments delete --comment 67890 --type inline --confirmOptions:
| Flag | Description |
|---|---|
--comment | Comment ID |
--type | Comment type: footer (default), inline |
--confirm | Skip confirmation prompt |
Sync Behavior
Section titled “Sync Behavior”During docs pull and docs push:
- Comments are not synced by default (they’re metadata, not content)
- Use
--include-commentsto export comments alongside pages - atlcli preserves comment IDs in a
.comments.jsonsidecar file when exported
Export with Comments
Section titled “Export with Comments”atlcli wiki docs pull ./docs --include-commentsCreates files like:
docs/├── my-page.md└── my-page.comments.jsonComments File Format
Section titled “Comments File Format”{ "pageId": "12345", "comments": [ { "id": "67890", "type": "footer", "body": "Great documentation!", "author": "alice@company.com", "created": "2025-01-14T10:00:00Z", "resolved": false, "replies": [] } ]}JSON Output
Section titled “JSON Output”All comment commands support --json for scripting:
atlcli wiki page comments list --id 12345 --json{ "schemaVersion": "1", "comments": [ { "id": "67890", "type": "footer", "body": "Great documentation!", "author": { "displayName": "Alice", "email": "alice@company.com" }, "created": "2025-01-14T10:00:00Z", "resolved": false, "replies": [] } ], "total": 1}Use Cases
Section titled “Use Cases”Code Review Workflow
Section titled “Code Review Workflow”# List unresolved commentsatlcli wiki page comments list --id 12345 --json | jq '.comments[] | select(.resolved == false)'
# Resolve after addressingatlcli wiki page comments resolve --comment 67890Bulk Comment Export
Section titled “Bulk Comment Export”# Export all comments from a spacefor page in $(atlcli wiki page list --space TEAM --json | jq -r '.pages[].id'); do atlcli wiki page comments list --id $page --json > "comments-$page.json"doneFind Pages with Unresolved Comments
Section titled “Find Pages with Unresolved Comments”# Check each page for unresolved commentsfor page in $(atlcli wiki page list --space TEAM --json | jq -r '.pages[].id'); do COUNT=$(atlcli wiki page comments list --id $page --json | jq '[.comments[] | select(.resolved == false)] | length') if [ "$COUNT" -gt 0 ]; then echo "Page $page has $COUNT unresolved comments" fidoneRelated Topics
Section titled “Related Topics”
Jira and Confluence are trademarks of Atlassian Corporation Plc.
atlcli is not affiliated with, endorsed by, or sponsored by Atlassian.