| name | zentao-fix-bug |
| description | Use when Codex needs to read, analyze, fix, verify, or write back ZenTao bugs through zentao_* MCP tools. Trigger for requests that mention a ZenTao Bug ID, ZenTao defect fixing, Bug attachments, my work lists, product/project/execution Bug lists, REST v1 ZenTao routes, or safe assign/resolve/close/writeback actions after a code fix. |
ZenTao Fix Bug
Overview
Use the zentao_* MCP tools as the source of ZenTao truth, then perform code changes in the target business repository. Keep this entry file light: load only the module references needed for the current request.
Module Index
- Start any ZenTao Bug repair with workflow-bugfix.md, mcp-tools.md, and api-bugs.md.
- When using
zentao_call_api for an unfamiliar REST v1 route, read api-catalog.md.
- When the Bug needs product, project, execution, story, task, build, testcase, user, module, option, or required-field context, read api-context.md.
- Before assign, resolve, close, activate, confirm, update, create, delete, or any non-GET REST call, read write-actions.md.
- Before downloading or interpreting attachments, read attachments.md.
- When a route is missing, a write is rejected, or tool output is surprising, read failure-handling.md.
Hard Rules
- Process one Bug at a time unless the user explicitly asks for triage.
- Prefer scenario tools before generic REST calls:
zentao_get_bug, zentao_list_my_work, zentao_list_bugs, zentao_download_file, zentao_confirm_bug, and zentao_resolve_bug.
- When the user asks for current-user work or Bug lists without product/project/execution scope, call
zentao_list_my_work first; it defaults to assigned Bugs and does not need a product ID.
- Use
zentao_search_api before any unfamiliar zentao_call_api route.
- Pass catalog template paths to
zentao_call_api, such as /bugs/:id; put concrete IDs in pathParams.
- Use
dryRun=true before any non-GET call.
- Do not assign, resolve, close, delete, or otherwise change ZenTao state unless the user explicitly asks.
- Do not use legacy or page-scraping fallbacks for missing REST v1 routes.
- Do not modify the ZenTao source checkout while fixing a business Bug.
Default Flow
- Load the Bug and relevant ZenTao context.
- Inspect attachments only when they matter to reproduction or expected behavior.
- Fix code in the target business repository using that repository's conventions.
- Run focused verification, then broader checks when the change affects shared behavior.
- Prepare a writeback report. Write to ZenTao only when the user requested it and safety switches allow it.
