Bug tracker — overview
Complex QA includes a built-in bug tracker as part of the TMS. Defects live in a project and team alongside test cases and runs—no separate product and no required external integration.
The model aligns with Jira, Bugzilla, and TestRail defects: separate status and resolution, priority and severity, and text blocks for reproduction and product versions.
Place in the product
text
Team
└── Project
├── Test management (TMS) — cases, runs, results
├── Bug tracker — bugs (defects)
└── Execution context — environment snapshots (see TMS)The bug tracker is available from the project card and sidebar. The Tasks view can include bugs assigned to you via the assignee field.
Bug entity
| Field / group | Purpose |
|---|---|
bug_title | Short title (listing and details header) |
bug_description | Problem description (HTML) |
bug_reproduction_steps | Steps to reproduce |
bug_expected_result / bug_actual_result | Expected vs actual outcome |
bug_type | Type: BUG, REGRESSION, PERFORMANCE, SECURITY, … |
bug_status | Workflow status: OPEN, TRIAGE, IN_PROGRESS, RESOLVED, CLOSED, … |
bug_resolution | Outcome when closing: FIXED, WONT_FIX, DUPLICATE, … |
bug_priority / bug_severity | Fix queue vs product impact |
reporter_id / assigned_to | Reporter and assignee (team members) |
bug_build_version, bug_affected_version, bug_fixed_version | Product versions (not browser/OS environment) |
duplicate_of_id | Link to duplicate (another bug’s ID) |
Full field list, statuses, and typical actions are on Bugs.
Links to TMS and environment
- Execution context snapshots (browser, OS, URL catalogs, etc.) are documented separately: Execution context. A single free-text “environment” field on a bug does not replace structured context.
- Bug ↔ test case / run result links are planned in the data model; a one-click “create bug from Failed” flow may not be in the UI yet.
- External trackers (Jira, GitHub, etc.) are on the roadmap; work happens inside Complex QA today.
Detail pages
| Version | 1.1 |
| Last updated | 2026-06-13 |