Transition Issue
jira_transition_issueDestructive
Transition a Jira issue to a new status by providing the issue key and transition ID. Optionally update fields or add a comment in Markdown format.
Instructions
Transition a Jira issue to a new status.
Args: ctx: The FastMCP context. issue_key: Jira issue key. transition_id: ID of the transition. fields: Optional JSON string of fields to update during transition. comment: Optional comment for the transition in Markdown format.
Returns: JSON string representing the updated issue object.
Raises: ValueError: If required fields missing, invalid input, in read-only mode, or Jira client unavailable.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| issue_key | Yes | Jira issue key (e.g., 'PROJ-123', 'ACV2-642') | |
| transition_id | Yes | ID of the transition to perform. Use the jira_get_transitions tool first to get the available transition IDs for the issue. Example values: '11', '21', '31' | |
| fields | No | (Optional) JSON string of fields to update during the transition. Some transitions require specific fields to be set (e.g., resolution). Example: '{"resolution": {"name": "Fixed"}}' | |
| comment | No | (Optional) Comment to add during the transition in Markdown format. This will be visible in the issue history. |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |