Transition issue
jira_transition_issueAdvance a Jira issue through its workflow by providing a transition name or ID; it validates against current status and handles required fields and comments.
Instructions
Move one issue through its workflow. transition takes the transition's NAME or id and is resolved against the transitions available from the issue's CURRENT status at call time; an unresolvable value comes back as a validation error listing the valid ones, and nothing is sent. Status cannot be set through jira_update_issue. Screens that demand a resolution take it in fields.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| apply | No | Set true to EXECUTE this write. Omit (or false) to get a plan of the request that would be sent. Executing also requires the server to run with JIRA_WRITE_MODE=apply. | |
| issue | Yes | Issue key (PROJ-123) or numeric issue id. | |
| fields | No | Fields the transition screen demands, e.g. { "resolution": { "name": "Done" } }. jira_get_transitions reports which ones have a screen. | |
| format | No | How to interpret a string rich-text input: "text" (default — blank lines split paragraphs, single newlines are hard breaks) or "markdown" (the documented subset: headings, lists, code fences, bold/italic/code, links). Refused alongside a raw ADF document. | |
| comment | No | Comment added as part of the transition; text or ADF. | |
| plan_id | No | The single-use id returned by the preceding plan-mode call. Required together with apply: true; a mismatch means the arguments changed since the plan, and the write is refused rather than executed. | |
| profile | No | Named credential profile for this call. Omit to use the active profile. Rejected when the server locks the profile (JIRA_LOCK_PROFILE). | |
| transition | Yes | Transition NAME (Start Progress) or id (31). Resolved against the transitions available from this issue's current status. |