resolve_bug
Resolve a bug by ID with required structured solution modules covering root cause, fix approach, logic change, and impact; specify resolved build.
Instructions
Resolve one bug by ID via POST /bugs/{id}/resolve. REQUIREs non-empty solutionModules {rootCause, fixApproach, logicChange, impact} — without it the resolve call will REJECT with an error. Plain comment/solution is no longer accepted. Many instances require resolvedBuild (解决版本); pass it or set ZENTAO_DEFAULT_RESOLVED_BUILD (e.g. trunk). Do NOT use raw HTTP PUT/edit as a resolve substitute — it only flips status without writing solution text.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Bug ID | |
| comment | No | IGNORED for resolve — only solutionModules is accepted. This field only appends plain text to the action record if solutionModules is also present. | |
| solution | No | IGNORED for resolve — only solutionModules is accepted. This field is kept for backward compatibility only. | |
| resolution | No | Default fixed | |
| resolvedBuild | No | 解决版本 (required by many instances). Falls back to ZENTAO_DEFAULT_RESOLVED_BUILD. Common value: trunk | |
| solutionModules | No | REQUIRED — resolve WILL REJECT without it. Structured solution object. Server formats into multi-line text with 【根因】【修复思路】【改动逻辑】【影响范围】. At least one field must be non-empty. |