Assign Issue: Jira action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Issue Key or ID issue_key	string	Required	The issue key (e.g. PROJ-123) or numeric ID
Assignee Account ID accountId	string	Optional	Atlassian account ID of the user to assign. Leave empty to unassign.

Sample request

{
  "issue_key": "e.g. PROJ-123",
  "accountId": "e.g. 5b10a2844c20165700ede21g"
}

Returns

{
  "success": true
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Assign Issue.

What does the Assign Issue action do in Jira?

Assigns a Jira issue to a user (by accountId) or unassigns it. The standard routing action for AI-driven triage or rotating on-call assignment.

What inputs does Assign Issue require?

Required: Issue Key or ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Jira returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Assign Issue support batch operations?

Yes. Run Assign Issue inside a Loop node to process arrays. Tiny Command handles Jira's rate limits automatically so you don't have to throttle manually.

More actions