Bugs
Bugs
This section covers defects recorded in a ComplexQA project. The SDK type is bug. On Russian pages the domain term is дефект.
Use this section when you create, edit, or link bugs to test cases, test run results, or execution context. Bugs live in the same project as your test documentation - they are not a separate product.
Manual test execution stays under Test runs. Automated checks stay under Autotests.
Boundaries
- A bug belongs to one project and one team.
- Status and resolution are separate fields. Priority and severity are separate fields.
- Screenshots attach on the bug details page. File storage is shared with Files.
- External trackers (for example Jira) are not required and are not covered here.
In this section
| Page | Purpose |
|---|---|
| Bug | Element reference: fields, enumerations, screenshots, relations |
| Bug creation | How to create a bug from the listing or from a test run result |
| Linking a bug to a test case | How to add or remove relation links |
What to read next
- Create and classify a defect: Bug creation.
- Connect it to the case or result that found it: Linking a bug to a test case.
- Check field meanings and enums: Bug.
Did this page help?