issue/update resource: issue

When to Use

• Assignee re-routing: When a team member goes on leave, a scheduled workflow queries their open issues and uses issue/update to reassign each one to a backup engineer, ensuring no issue is unattended during the absence.
• Priority escalation from monitoring: If a monitoring system detects that an existing incident is worsening (e.g. error rate climbs from 5% to 40%), a workflow automatically updates the corresponding Jira bug's priority from High to Highest and appends escalation context to the description.
• Fix version stamping: At release branch cut, a workflow queries all "In Progress" issues in the sprint and sets their fixVersion field to the new release version identifier, enabling accurate release tracking.
• Label management: A post-deployment verification workflow updates all issues deployed in a release by adding the deployed-prod label and setting a custom field with the deployment timestamp.
• Story point synchronisation: When a planning tool exports updated estimates, a batch workflow reads the estimates and updates the storyPoints custom field on the corresponding Jira stories to keep planning data in sync.

Configuration

Connection

Operation Fields

Sample Configuration

Escalate a bug's priority and update its description after worsening alert metrics:

{
  "resource": "issue",
  "operation": "update",
  "Host": "https://acmecorp.atlassian.net",
  "Email": "automation@acmecorp.com",
  "ApiToken": "{{ $credentials.jiraApiToken }}",
  "IssueKey": "{{ $json.issueKey }}",
  "Fields": {
    "priority": { "name": "Highest" },
    "description": "{{ $json.originalDescription }}\n\n---\n**ESCALATED {{ $now }}**\nError rate climbed to {{ $json.errorRate }}%. Immediate attention required.\nAffected users: {{ $json.affectedUsers }}"
  },
  "CustomFields": {
    "customfield_10050": "{{ $json.incidentId }}"
  }
}

Validation Errors

Output Fields

Sample Output

{
  "status": "success",
  "issueKey": "OPS-347",
  "resource": "issue",
  "operation": "update"
}

Expression Reference

Node Policies & GuardRails

• Partial updates only: Only supply fields you intend to change. The Jira API performs a merge — omitted fields remain unchanged. Do not reconstruct the entire issue object for updates.
• No status change via update: The status field cannot be changed via issue/update. Status transitions must use issue/executeTransition. Attempting to set status via Fields will result in a FIELD_NOT_EDITABLE error.
• Account ID vs username: In Jira Cloud, assignee must be specified via accountId not name. Use user/get to resolve a username to an account ID if needed.
Labels replace not append:Setting the labels field replaces the entire label array. To add a label, first fetch the current labels via issue/get, append the new label, and set the full array.

Workflow Examples

Example 1 — Escalate Priority on Worsening Metric

// Monitoring webhook fires with worsening error rate
// Step 1: issue/get — fetch current issue state
// Step 2: IfCondition — {{ $json.errorRate }} > 30 AND {{ $output.getIssue.priority }} !== "Highest"
// Step 3 (if escalation warranted): issue/update
{
  "resource": "issue",
  "operation": "update",
  "IssueKey": "{{ $json.issueKey }}",
  "Fields": {
    "priority": { "name": "Highest" },
    "labels": ["production", "escalated", "p0"]
  }
}
// Step 4: Slack/postMessage — notify manager channel

Example 2 — Bulk Reassign on Team Member Absence

// Step 1: issue/getAll
{
  "Jql": "assignee = \"{{ $json.absentUser }}\" AND status != Done"
}
// Step 2: Loop over issues
// Step 3 per issue: issue/update
{
  "resource": "issue",
  "operation": "update",
  "IssueKey": "{{ $loopItem.key }}",
  "Fields": {
    "assignee": { "accountId": "{{ $json.backupUser.accountId }}" }
  }
}