Edit a defect or change its status

defect.updateChanges dataCreates, updates or deletes something in your workspace.

What it does

Changes a defect of the connected workspace: title, description, severity, status, priority, the release it affects, and its bug breakdown. Send only the fields to change. Typical use: move it to in_progress when work starts, fixed when the fix is merged, verified once its regression case passes, or closed / wont_fix. Statuses: open, in_progress, fixed, verified, closed, wont_fix; open, in_progress and fixed still count against the release's ship gate (release.readiness). Breakdown lists (acceptanceCriteria, edgeCases) replace the stored list when given; the two default acceptance criteria are always kept. It does not edit the issue already filed in GitLab / Jira. Get the id from defect.list. Returns {success, data: the updated defect}.

Ask your agent

You don’t call defect.update yourself. Say something like this to Claude Code, Cursor or another MCP-connected agent:

  • “The checkout defect is fixed, mark it so”
  • “Lower the login bug to minor”
  • “Move the cart defect to the July release”

Inputs

NameTypeDescription
defectId
required
stringId of the defect (the id from defect.list).
title
optional
stringNew short summary.
description
optional
string | nullNew description, markdown; null clears it.
severity
optional
enumblocker, critical, major, minor or trivial.
Allowed: blockercriticalmajorminortrivial
status
optional
enumNew status: open, in_progress, fixed, verified, closed, wont_fix.
Allowed: openin_progressfixedverifiedclosedwont_fix
priority
optional
enum | nullP0 (most urgent) to P3; null clears it.
releaseId
optional
string | nullRelease it affects (the id from release.list); null unlinks it.
acceptanceCriteria
optional
string[]Acceptance criteria for the fix; replaces the stored list (the two defaults are always kept).
edgeCases
optional
string[]Edge cases the fix must handle; replaces the stored list.
technicalNotes
optional
string | nullLikely cause, area of the code, or fix notes; null clears them.

The MCP call

What the agent’s MCP client sends (placeholders in angle brackets):

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "defect.update",
    "arguments": {
      "defectId": "<defectId>"
    }
  }
}

Connect your agent

npx -y @testmaze/mcp init tmt_xxx
claude mcp add tm --scope project -- npx -y @testmaze/mcp

Create the token in your Test Maze workspace under Settings → MCP. Setup for Cursor, Cline, Gemini CLI and Codex CLI is shown there too.