Skip to main content
Glama

Transition Jira issue

transition_issue

Transitions a Jira issue by transition ID, transition name, or target status, optionally adding a plain-text comment and resolution, then returns the new status and completion dates.

Instructions

Transition a Jira issue using a transition ID or a case-insensitive transition or target status name. An optional plain-text comment is posted with the transition when the screen accepts comments. Otherwise, it is posted immediately afterwards. Resolution and fields must be accepted by the transition screen. Returns the new status, resolution, and resolutiondate. Jira sets resolutiondate itself. The API cannot edit it. Record the actual completion date in the comment.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "issue_key": "<issue_key>",
      "transition": "<transition>"
    },
    "name": "transition_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoTransition-screen fields in Jira REST format, keyed by field ID as returned by get_transitions.
commentNoPlain-text comment to add with the transition.
config_idNoJira instance to use, from list_configs. Omit for the default.
issue_keyYesIssue key, e.g. ONE-123.
resolutionNoResolution name, e.g. Fixed.
transitionYesTransition ID, transition name, or target status name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description adds substantial behavior beyond the annotations: it explains comment timing relative to the transition screen, that resolution and fields must be accepted by that screen, that the return includes new status/resolution/resolutiondate, and that Jira controls resolutiondate so the actual completion date must be recorded in the comment.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core action and then covers side effects and return values efficiently. It is slightly long but every sentence contributes operational detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, but the description explains the important return values and the resolutiondate constraint. For a non-idempotent, open-world mutation tool with complete parameter coverage and existing annotations, this is nearly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the input schema already documents all six parameters. The description still adds useful semantics by clarifying that transition accepts an ID, name, or target status name and by explaining how comment, resolution, and fields interact with the transition screen.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Transition a Jira issue') and distinguishes the operation from generic updates by explaining that it uses a transition ID, transition name, or target status name. An agent can tell this is the status-workflow tool rather than update_issue or add_comment.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly implies when to use the tool: changing an issue's workflow status. However, it does not explicitly compare this with alternatives such as update_issue or say that get_transitions should be called first when the transition is unknown.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.