Bugs

A bug is a defect within a project. It belongs to a team and project (project_id, team_id).

---

Where to open

1. Open a project (card or details).
2. Go to Bugs (project-scoped listing).
3. Tabs:
   • Opened - filter by OPEN status;
   • All - full project bug list.

---

Typical actions

Action	How
Create	Add button on the listing; creates a project row (title can be set in details).
Open details	Click a table row.
Edit	Inline in the table (status, priority, type, …) or on the details page.
Delete	Button on the details page.
Bulk actions	Table context menu (multi clone/delete where enabled in the UI).
Copy value	Right-click a data cell → Copy value (displayed text, not raw IDs). See Tables and context menu.

Bug clone may not be available yet-follow what you see in the app.

---

Details page

Layout matches other TMS entities:

1. Title (bug_title) - editable in the app bar.
2. Details tab - pivot table of attributes:
   • status, type, priority, severity, resolution (colored selects);
   • reporter (reporter_id) and assignee (assigned_to) - team member pickers;
   • build / affected / fixed versions;
   • duplicate_of_id - numeric ID of another bug.
3. Rich text blocks:
   • description;
   • reproduction steps;
   • expected result;
   • actual result.
4. Plain text tab - copy-friendly view of key fields.
5. Link tabs (relations to TMS and environment):
   • Test cases - cases related to this bug; Add opens a selection dialog; remove via row context menu.
   • Test run results - results where the defect was seen; same link/unlink pattern.
   • Execution context - environment snapshots tied to the bug; table shows browser, OS, URL, build, and other listing columns.

Changes are saved to the server as you edit; the table shows a loading overlay while the API responds.

---

Links to TMS and environment

Relations use the bug_relation entity: each row links one bug to one target via relation_type and element_id.

Tab on bug details	Target	Typical use
Test cases	test_case_id	Defect applies to a case in general (refs)
Test run results	test_run_result_id	Found during a specific run (defect)
Execution context	execution_context_id	Reproduction environment snapshot

The reverse view exists on test case, test run result, and execution context details - tab Bugs.

Linking is manual (dialog + checkboxes). There is no automatic “create bug from Failed” button yet.

---

Classification

Type (bug_type)

BUG, REGRESSION, PERFORMANCE, SECURITY, USABILITY, COMPATIBILITY, DOCUMENTATION, OTHER.

Status (bug_status)

OPEN, TRIAGE, IN_PROGRESS, ON_HOLD, RESOLVED, CLOSED, REOPENED.

Resolution (bug_resolution)

Used when closing: FIXED, WONT_FIX, DUPLICATE, CANNOT_REPRODUCE, WORKS_AS_DESIGNED, DEFERRED, NOT_A_BUG.

Priority and severity

• Priority (bug_priority): CRITICAL, HIGH, NORMAL, LOW - fix queue order.
• Severity (bug_severity): BLOCKER, CRITICAL, MAJOR, MINOR, TRIVIAL - user/product impact.

Status and resolution are separate (Jira/Bugzilla pattern): status is workflow stage, resolution is the close outcome.

---

Product versions

Field	Meaning
bug_build_version	Build where the defect was found
bug_affected_version	Affected releases
bug_fixed_version	Version where it was fixed

These are product fields, not browser/OS catalogs. Structured reproduction environment uses execution context snapshots - link them on the Execution context tab.

---

Not available yet

To set expectations:

• No one-click bug from failed run result (link manually via tabs).
• No Jira/GitHub sync out of the box.
• No labels or “blocks/depends on” graph-only duplicate_of_id and bug_relation links above.

---

See also

• Bug tracker overview
• Execution context
• Test run results
• Recommended workflow

---

Version	1.2
Last updated	2026-06-14