Skip to main content
Glama

jira_get_transitions

Retrieve available workflow transitions for a Jira issue to understand possible next status changes and actions.

Instructions

Get available transitions for a Jira issue

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issueKeyYesThe Jira issue key

Implementation Reference

  • MCP server tool handler that validates input using GetTransitionsSchema and calls jiraClient.getTransitions(issueKey)
    case "jira_get_transitions": { const { issueKey } = GetTransitionsSchema.parse(args); const transitions = await jiraClient.getTransitions(issueKey); return { content: [ { type: "text", text: JSON.stringify(transitions, null, 2) }, ], }; }
  • Core implementation in JiraClient: makes API request to /rest/api/2/issue/{issueKey}/transitions to fetch available transitions
    issueKey: string ): Promise<{ transitions: JiraTransition[] }> { return this.request<{ transitions: JiraTransition[] }>( `/issue/${issueKey}/transitions` ); }
  • Zod schema for input validation: requires issueKey string
    const GetTransitionsSchema = z.object({ issueKey: z.string().describe("The Jira issue key"), });
  • src/index.ts:347-357 (registration)
    Tool registration in MCP server's listTools response, including name, description, and inputSchema
    { name: "jira_get_transitions", description: "Get available transitions for a Jira issue", inputSchema: { type: "object", properties: { issueKey: { type: "string", description: "The Jira issue key" }, }, required: ["issueKey"], }, },

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yogeshhrathod/JiraMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server