jira issue comment add¶
- Usage:
jira issue comment add KEY... [flags]
Add the same comment to one or more issues. Use Markdown for quick terminal notes or --json-input when an agent already has a native ADF comment body.
The comment body runs through the validate-and-encode ADF pipeline before submission. --dry-run previews the validated ADF and does not contact Jira. Visibility can be restricted by Jira role or group.
Input¶
--json-input <FILE>¶
Comment body as native ADF JSON file (canonical for agents)
Accepts a file.
--markdown <MARKDOWN>¶
Comment body as Markdown (lossy convenience layer)
--markdown-file <FILE>¶
Read the Markdown body from a file; - reads stdin
Accepts a file.
Visibility¶
--visibility-group <GROUP>¶
Restrict comment to a Jira group
--visibility-role <ROLE>¶
Restrict comment to a Jira role (e.g. Developers)
Safety¶
--dry-run¶
Preview mutation without submitting
Execution¶
-p --parallelism <N>¶
Maximum concurrent requests (1-16)
Default: 1
Output fields¶
With --output json, the response envelope's data object carries these fields. Run jira agent schema for the full machine-readable schema.
| Field | Type | Description |
|---|---|---|
comment |
object | null | |
dry_run |
boolean | |
issue.id |
string | |
issue.key |
string | |
issue.self |
string | |
warnings[].field |
string | |
warnings[].lossy |
boolean | |
warnings[].mark_type |
string | |
warnings[].message |
string | |
warnings[].node_type |
string | |
warnings[].path |
string | |
warnings[].type |
string |
Examples¶
jira issue comment add PROJ-123 --markdown "Deployed to staging." # (1)!
jira issue comment add PROJ-123 --json-input ./comment.json # (2)!
jira issue comment add PROJ-123 --markdown "Internal note." --visibility-role Developers # (3)!
jira issue comment add PROJ-123 --markdown "Draft note." --dry-run --output=json # (4)!
- Add a Markdown comment to an issue
- Add a comment from a native ADF JSON file
- Restrict a comment to a Jira role
- Preview a comment for an agent