Update Issue

jira.update_issue

ActionBusiness appsconnection required

Calls the Jira Cloud REST API with the connection's email and API token.

Change fields on an existing Jira issue.

Ask about Jira All Jira nodes Provider API docs ↗

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

6 fields, 1 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	—	—	—
summary New summary line for the issue.	string	No	—	—	—
description New description — plain text, or an ADF document as JSON.	string	No	—	—	—
fields Any other fields to set, as a JSON object of field id to value, e.g. {"priority": {"name": "High"}, "customfield_10011": "Q3"}. Merged under summary and description.	object	No	—	—	{"priority":{"name":"High"}}
update Jira's verb form for fields that are added to rather than replaced, e.g. {"labels": [{"add": "urgent"}]}.	object	No	—	—	{"labels":[{"add":"urgent"}]}
notify_users Email the issue's watchers about the edit. On by default, as in Jira.	boolean	No	true	—	—

At least one of summary, description, fields, update must be set.

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "fields": {
    "priority": {
      "name": "High"
    }
  },
  "notify_users": true,
  "update": {
    "labels": [
      {
        "add": "urgent"
      }
    ]
  }
}

Output

One shape.

result

Field	Type	Example
ok True when Jira accepted the call.	boolean	—
key The issue key the call acted on.	string	PROJ-123

{
  "key": "PROJ-123",
  "ok": false
}

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.
Custom fields are keyed by id, not label: 'customfield_10011'. Run jira.list_fields once to map a field's name to its id.

Related Jira nodes

Templates that use Jira

Solutions with Jira

See Update Issue 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.

Book a technical demo Talk to sales