Update Issue
update_issueUpdate specific fields of a MantisBT issue using partial PATCH, such as status, resolution, priority, and custom fields, with an optional note appended.
Instructions
Update one or more fields of an existing MantisBT issue using a partial PATCH.
The "fields" object accepts any combination of:
summary (string)
description (string)
steps_to_reproduce (string)
additional_information (string)
status: { name: "new"|"feedback"|"acknowledged"|"confirmed"|"assigned"|"resolved"|"closed" }
resolution: { id: 20 } (20 = fixed/resolved)
handler: { id: } or { name: "" }
priority: { name: "" }
severity: { name: "" }
reproducibility: { name: "" }
category: { name: "" }
version: { name: "" } (affected version)
target_version: { name: "" }
fixed_in_version: { name: "" }
view_state: { name: "public"|"private" }
custom_fields: [{field: {id|name}, value: ""}] (only the listed custom fields are changed, others stay untouched; use get_issue_fields to discover fields)
Important: when resolving an issue, always set BOTH status and resolution to avoid leaving resolution as "open".
Use the optional "note" parameter to append a note in the same call (e.g. the reason for a status change) — no separate add_note call needed. For a note without field changes use add_note.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Numeric issue ID to update | |
| note | No | Optional note text appended after a successful update (e.g. reason for a status change). Replaces a separate add_note call. | |
| fields | Yes | Fields to update (partial update — only provided fields are changed; unknown keys are rejected) | |
| dry_run | No | If true, return the patch payload that would be sent without actually updating the issue. Useful for previewing changes before committing them. | |
| note_view_state | No | Visibility of the appended note: "public" (default) or "private". Only used when "note" is set. | public |