Jira - Transition Issue

↩ Part of the Jira integration.

Description

Executes a workflow transition on an issue (POST /issue/{key}/transitions) — this is how you move a ticket from To Do to In Progress, or close it as Done.

You can pass either a numeric transition id or a transition name. If you pass a name, the node first calls GET /issue/{key}/transitions, finds the matching transition for that issue’s current status and uses its id.

Configuration

Field	Type	Required	Description
`credentials_id`	credentials	Yes	Jira credential
`issue_key`	text	Yes	Issue key (e.g. `OPS-123`)
`transition`	text	Yes	Transition id (e.g. `31`) or name (e.g. `In Progress`)

Both issue_key and transition accept dynamic variables.

Credentials

This module requires a Jira (Atlassian) credential:

Field	Description
`base_url`	Site URL, e.g. `https://your-domain.atlassian.net`
`email`	Atlassian account email
`api_token`	API token from id.atlassian.com

Output

Jira returns an empty body, so the node returns a confirmation object with the id it actually used:

{
  "key": "OPS-123",
  "transitioned": true,
  "transitionId": "31"
}

Along with it, _meta:

{ "moduleVersion": "1.0.0", "success": true, "key": "OPS-123", "transitionId": "31", "totalMs": 520 }

Usage Example

By name (recommended)

{
  "credentials_id": "jira_ops",
  "issue_key": "OPS-123",
  "transition": "In Progress"
}

By id (one call less)

{
  "credentials_id": "jira_ops",
  "issue_key": "OPS-123",
  "transition": "31"
}

Driven by previous data

{
  "credentials_id": "jira_ops",
  "issue_key": "{{data.key}}",
  "transition": "{{data.target_status}}"
}

Notes

Transition ids are project-specific. They come from each project’s workflow scheme, so an id that works in OPS may not exist in DEV. Using the name is safer across projects.
Name matching is case-insensitive and also matches the destination status name (t.to.name), so both Done and the transition labelled Close issue can resolve depending on your workflow.
If the name is not among the issue’s available transitions, the error message lists the valid ones for that issue — a fast way to discover the right label.
Only transitions available from the issue’s current status are valid. A ticket already in Done cannot be transitioned to Done again.
Anything a transition screen marks as required (a resolution, a comment) must be set beforehand — this node sends only the transition, no extra fields.

Jira: Get issue — check the current status before transitioning.
Jira: Update issue — set fields a transition screen may require.
Jira: Search issues — find every issue to move in one pass.