ActionJiraUpdated September 2026

How do I assign a Jira issue?

Short answer: You can assign issue in Jira by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Jira Assign Issue action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Assign Issue in Jira — start free
Inputs

The fields this action accepts.

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

FieldTypeRequiredDescription
Issue Key or ID
issue_key
stringRequiredThe issue key (e.g. PROJ-123) or numeric ID
Assignee Account ID
accountId
stringOptionalAtlassian 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.

Triggered by

Apps that pair well as the trigger for Assign Issue.

Any of these apps can fire this action as part of a workflow.

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 run history shows the failed step with its input and the error message Jira returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Assign Issue support batch operations?
Run Assign Issue inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Jira's rate limits.
More actions

Other Jira actions.

Assign Issue in Jira — start free