batch_resolve_my_bugs
Resolve multiple active bugs at once with fixed resolution. The batch requires shared solution modules covering root cause, fix approach, logic change, and impact.
Instructions
Batch resolve my bugs via the real resolve API (default status=active, resolution=fixed). REQUIRES shared non-empty solutionModules {rootCause, fixApproach, logicChange, impact} — without it the batch will REJECT with an error. Plain comment/solution is no longer accepted. Requires resolvedBuild or ZENTAO_DEFAULT_RESOLVED_BUILD on instances that validate 解决版本. Prefer projectSetId or /my/bug for project-set scope.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Default 1 | |
| path | No | Optional safe list path override. Allowed values: /bugs, /my/bug, /my/bugs. | |
| limit | No | List page size, default 50 | |
| status | No | Default active | |
| comment | No | IGNORED for resolve — only solutionModules is accepted. This field only appends plain text to the action record if solutionModules is also present. | |
| keyword | No | Optional keyword filter before resolve | |
| maxItems | No | Max resolve count, default 20 | |
| solution | No | IGNORED for resolve — only solutionModules is accepted. This field is kept for backward compatibility only. | |
| productId | No | Optional product id (for instances requiring product scope) | |
| projectId | No | Optional project id. Directly query /projects/{id}/bugs, no cross-project merge. | |
| resolution | No | Default fixed | |
| stopOnError | No | Default true; stop on first resolve failure | |
| projectSetId | No | Optional project-set id. Prefer this for project-set bugs, especially when the project set has no concrete project entries. | |
| resolvedBuild | No | Shared 解决版本 for the batch. Falls back to ZENTAO_DEFAULT_RESOLVED_BUILD. Common value: trunk | |
| solutionModules | No | REQUIRED — resolve WILL REJECT without it. Shared structured solution for the batch. Server formats into multi-line text with 【根因】【修复思路】【改动逻辑】【影响范围】. Write common root cause and shared logic changes. |