Skip to content

jira issue comment

  • Usage: jira issue comment KEY... [flags]

Add, list, edit, or delete Jira issue comments. Use the subcommands for explicit comment workflows, or pass issue keys directly for the legacy comment add behavior.

Comment bodies can be supplied as Markdown convenience input or native ADF JSON. Mutating comment commands run the body through the validate-and-encode ADF pipeline before submission.

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 PROJ-123 --markdown "Deployed to staging." # (1)!
jira issue comment PROJ-123 --json-input ./comment.json # (2)!
jira issue comment add PROJ-123 --markdown "Draft note" --dry-run # (3)!
  1. Add a comment using the legacy shorthand
  2. Add a comment from a native ADF JSON file
  3. Preview the comment without contacting Jira

Subcommands