bug_create
Creates a bug when the user asks to log a defect and publishes it right away: with an approver it goes to approval, otherwise to work to the assignee. Placement is one of: a feature (featureID or featureKey), a version (versionID) or the product backlog (productID); type is the criticality (the nature of the defect is the separate bugType field), and bugs always have a testing stage. Stage assignees: employee uuid, "any" (any employee) or null (no such stage; the work stage always exists). Returns the key, link, status and allowed transitions.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"title": "<title>",
"spec": "<spec>",
"gist": "<gist>",
"rulesRevision": "<rulesRevision>",
"type": "<type>"
},
"name": "bug_create"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ord | No | Position of the new bug, as ord in task edits; omitted - the end of the feature's plan. | |
| gist | Yes | Gist: one or two sentences, "problem → solution", up to 300 characters of plain text (no Markdown, links or task keys), in the language of the workspace data. | |
| spec | Yes | Bug description in Markdown (no HTML) following the bug creation template, in the language of the workspace data. | |
| type | Yes | Criticality by actual impact: bug_trivial - cosmetic; bug_minor - inconvenience with a workaround; bug_major - a function works wrong or part of a scenario is unavailable, the workaround is costly; bug_critical - a scenario is impossible, data is lost or corrupted, a section crashes; bug_block - blocks the product or all testing. In doubt between two levels - the higher one. | |
| build | No | Build in which the defect was reproduced, from the deployed version. | |
| fuzzy | No | Intermittent bug: does not reproduce every time. | |
| stage | No | Stand where the bug was reproduced: dev - development and autotests, alpha - manual QA, prod - production data. | |
| title | Yes | Bug title, up to 200 characters, in the language of the workspace data. | |
| labels | No | Labels. | |
| browser | No | Browser where the defect was reproduced. | |
| bugType | No | Defect nature: ui - interface, fn - functionality, ux - usability, spec - documentation; not the severity, which is type. | |
| devices | No | IDs of devices from the company's QA devices where the defect was reproduced. | |
| priority | No | Priority; a human decision, set only at the user's explicit request. | |
| featureID | No | Feature ID - the preferred placement | |
| moduleIDs | No | IDs of the modules (screens) where the defect is visible. | |
| productID | No | Product ID - the product backlog, last resort | |
| versionID | No | Version ID - when no feature fits | |
| featureKey | No | Feature key #F12; not with featureID | |
| componentIDs | No | IDs of the components where the defect is actually visible; empty if unsure. | |
| testAssignee | No | Tester: employee UUID or "any" (default) - bugs are always tested. | |
| workAssignee | No | Assignee; default "any". | |
| workTimePlan | No | Planned fix time in minutes, for the assignee's role level. | |
| rulesRevision | Yes | Revision of the bug creation template the spec follows. | |
| reviewAssignee | No | Reviewer; default - no review stage. | |
| approvalAssignee | No | Approver; when omitted - the person who asked for the item (set by the server), null - no approval stage. | |
| workIterationDate | No | A date within the work iteration, YYYY-MM-DD; defaults to the current iteration. |