jira_transition_issue
Move a Jira issue to a new status by specifying the transition ID and issue key. Optionally add a comment or update fields during the transition using JSON input.
Instructions
Transition a Jira issue to a new status
Input Schema
Name | Required | Description | Default |
---|---|---|---|
comment | No | Comment to add during the transition (optional). This will be visible in the issue history. | |
fields | No | JSON string of fields to update during the transition. Some transitions require specific fields to be set. Example: '{"resolution": {"name": "Fixed"}}' | {} |
issue_key | Yes | Jira issue key (e.g., 'PROJ-123') | |
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' |
Input Schema (JSON Schema)
You must be authenticated.
Other Tools from MCP Atlassian
- confluence_attach_content
- confluence_create_page
- confluence_delete_page
- confluence_get_comments
- confluence_get_page
- confluence_get_page_ancestors
- confluence_get_page_children
- confluence_search
- confluence_update_page
- jira_add_comment
- jira_add_worklog
- jira_create_issue
- jira_delete_issue
- jira_download_attachments
- jira_get_agile_boards
- jira_get_board_issues
- jira_get_epic_issues
- jira_get_issue
- jira_get_project_issues
- jira_get_sprint_issues
- jira_get_sprints_from_board
- jira_get_transitions
- jira_get_worklog
- jira_link_to_epic
- jira_search
- jira_transition_issue
- jira_update_issue
Related Tools
- @sooperset/mcp-atlassian
- @1broseidon/mcp-jira-server
- @1broseidon/mcp-jira-server
- @George5562/Jira-MCP-Server
- @sooperset/mcp-atlassian