[SaintPatrck]

🎟️ Tracking

Extends the opt-in Jira write tools in the Atlassian MCP server.

📔 Objective

Callers can now move a Jira issue to a status by name with transition_issue, so a skill or automation can mark a ticket In Progress or Done without knowing its workflow.

Jira's transition API only takes a transition id, which varies by workflow and current status, so none of our write tools could change status.

An issue already in the target status is a no-op, so repeated calls are safe. When two transitions reach the same status, the first one Jira lists wins, and the dry run names it before anything is sent.

🤖 AI-assisted review

Standard local review (code-review-local): approved with no findings, none deferred.

[github-actions]

🤖 Bitwarden Claude Code Review

Overall Assessment: APPROVE

Reviewed the new opt-in transition_issue write tool in the Atlassian MCP server, along with its JiraClient transition methods, the JiraTransition type, the Zod schema, the specs, the README updates, and the 2.9.0 version bump across the marketplace, plugin manifest, README catalog, and changelog. The tool follows the existing write-tool pattern: dry run by default, live writes gated on the write token, and write errors and the scope hint going through the shared write-guard helpers. The issue key is validated against the shared JiraIssueKey pattern before it goes into the REST path, and the status lookup and the read-back after a transition both use the read-only client, so the write token is used only for the POST itself.