Update Comment
jira.update_comment
ActionBusiness appsconnection required
Calls the Jira Cloud REST API with the connection's email and API token.
Rewrite the body of an existing Jira comment.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Username & password
- Providers
- Jira
- Secret shape
- {"email", "api_token"}
- Config it needs
- domain
- Resolved by
- config.connection_id, else node.connection_id
Configuration
4 fields, 3 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
issue_key Issue key or numeric id, e.g. PROJ-123. Supports {{ }}. | string | Yes | — | — | — |
comment_id The comment's id, as returned by jira.add_comment or jira.list_comments. | string | Yes | — | — | — |
body The new comment text — plain text, or an ADF document as JSON. | string | Yes | — | — | — |
notify_users Email the issue's watchers about the edit. On by default, as in Jira. | boolean | No | true | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"notify_users": true
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok True when Jira accepted the call. | boolean | — |
comment_id The comment that was rewritten. | string | — |
updated When Jira recorded the edit, ISO-8601. | string | — |
{
"comment_id": "",
"ok": false,
"updated": ""
}Notes
- Rich text takes plain text — one paragraph per line — or a full Atlassian Document Format document written as JSON. Jira Cloud v3 stores only ADF, so a plain string sent straight to the API is what makes a field render empty.
See Update Comment run in a workflow.
In a technical demo we add the Jira connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.