ActionJiraUpdated September 2026
How do I move a Jira issue to a new status?
Short answer: You can transition issue in Jira by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Jira Transition 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.
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 | Issue Key or ID. Example: PROJ-123 |
Transition ID transition_id | string | Required | The numeric ID of the transition. Use 'Get Issue' and check available transitions, or find them in your Jira workflow settings. |
Sample request
{"issue_key": "e.g. PROJ-123","transition_id": "e.g. 31"}
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 Transition Issue.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Transition Issue.
What does the Transition Issue action do in Jira?
Changes the status of a Jira issue (e.g. To Do to In Progress to Done) by transition ID. Get the available transition IDs via Get Transitions first.
What inputs does Transition Issue require?
Required: Issue Key or ID, Transition 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 Transition Issue support batch operations?
Run Transition 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.
Action
Add Comment
Adds a comment to an existing Jira issue with optional visibility restriction (role or group). Used for automation activity logs, AI summary notes, or external system pings.
ActionAdd Watcher
Adds a user as a watcher on a Jira issue so they receive notifications on updates. Used to auto-loop in interested parties (PMs, designers, support).
ActionAssign Issue
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.
ActionCreate Issue
Creates a new issue (story, task, bug, epic, etc.) in a Jira project with summary, description, type, assignee, priority, labels, components, and custom fields. Standard write for converting external alerts into tracked work.
ActionDelete Issue
Permanently deletes a Jira issue by key or ID. Irreversible; pass deleteSubtasks=true to also remove children. Most teams transition to a Cancelled status instead.
ActionGet Issue
Retrieves a Jira issue by its key (ABC-123) or numeric ID with summary, description, status, assignee, comments, and custom fields. The standard read after a trigger fires with an ID.