jira issue transition¶
- Usage:
jira issue transition KEY... [STATUS] [flags]
Move one or more issues to a workflow status. Use it when advancing work through Jira from a script or terminal triage session.
Give the target status as a trailing argument, such as In Progress, or pass a numeric transition ID. A status name is resolved against each issue's available transitions at runtime; the same name can map to different IDs across workflows.
With no target, the command lists available transitions instead of mutating. --dry-run is a local preview and echoes the requested target without resolving it through Jira.
Input¶
--json-input <FILE>¶
Read transition payload from JSON file (canonical for agents)
Accepts a file.
--markdown <MARKDOWN>¶
Transition comment as Markdown, posted atomically with the status change
--markdown-file <FILE>¶
Read the Markdown body from a file; - reads stdin
Accepts a file.
Transition¶
--transition <STATUS>¶
Transition id or status name (or pass the status as a positional argument)
Safety¶
--dry-run¶
Preview mutation without submitting
Validation¶
--validate-remote¶
With --dry-run, resolve the target against the issue's live transitions (read-only fetch)
Execution¶
-p --parallelism <N>¶
Maximum concurrent requests (1-16)
Default: 1
Examples¶
jira issue transition PROJ-123 # (1)!
jira issue transition PROJ-123 "In Progress" # (2)!
jira issue transition PROJ-123 PROJ-124 Done --dry-run # (3)!
- List available transitions for an issue
- Move an issue to a named status
- Preview transitioning several issues without contacting Jira