Skip to content
Floogos

Jira - Update Issue

↩ Part of the Jira integration.

Description

Section titled “Description”

Updates the fields of an existing issue (PUT /issue/{key}). You supply a JSON object with the fields to change; everything you do not mention stays untouched.

If you include description as a plain string, the node converts it to ADF for you before sending it.

Configuration

Section titled “Configuration”
FieldTypeRequiredDescription
credentials_idcredentialsYesJira credential
issue_keytextYesIssue key (e.g. OPS-123)
fieldsjsonYesFields to update, e.g. {"summary":"New title"}

issue_key accepts dynamic variables. fields is parsed as JSON and sent as-is — dynamic variables are not resolved inside it. If the string is not valid JSON the node fails with a validation error.

Credentials

Section titled “Credentials”

This module requires a Jira (Atlassian) credential:

FieldDescription
base_urlSite URL, e.g. https://your-domain.atlassian.net
emailAtlassian account email
api_tokenAPI token from id.atlassian.com

Output

Section titled “Output”

Jira’s PUT /issue/{key} returns an empty body, so the node returns a confirmation object:

{
  "key": "OPS-123",
  "updated": true
}

Along with it, _meta:

{ "moduleVersion": "1.0.0", "success": true, "key": "OPS-123", "totalMs": 240 }

Usage Example

Section titled “Usage Example”

Rename an issue

Section titled “Rename an issue”
{
  "credentials_id": "jira_ops",
  "issue_key": "OPS-123",
  "fields": { "summary": "Checkout returns 500 on card payments" }
}

Change priority and labels

Section titled “Change priority and labels”
{
  "credentials_id": "jira_ops",
  "issue_key": "{{data.key}}",
  "fields": {
    "priority": { "name": "Highest" },
    "labels": ["checkout", "regression"]
  }
}

Replace the description

Section titled “Replace the description”
{
  "credentials_id": "jira_ops",
  "issue_key": "OPS-123",
  "fields": {
    "description": "Confirmed in production.\nAffects 3% of orders."
  }
}

The plain string is converted to ADF automatically.

Notes

Section titled “Notes”
  • labels and other array fields are replaced, not appended.
  • Assigning a user requires the accountId, not the display name: {"assignee":{"accountId":"5b10a2…"}}.
  • Custom fields use their internal id, e.g. {"customfield_10011":"Sprint 12"}.
  • A 400 usually means the field does not exist on the issue’s edit screen, or the value has the wrong shape. Validation errors are not retried.
Section titled “Related Nodes”