Bug Tracker

The Bugs page (/bugs) surfaces every test run result that has a linked bug ticket, giving QA teams a single view of open defects without switching to a separate tool.

How a bug gets tracked

A bug entry is created when you link a ticket to a failed result in a test run:

1. Open a test run and find a FAILED or BROKEN result.
2. In the Bug ticket field, paste the Linear or Jira issue URL.
3. QA Hub extracts the ticket key (e.g., LIN-42) and saves it with the result.

That result immediately appears on the Bugs page.

Bug lifecycle

Linear status polling

When your active connector is Linear, QA Hub polls linked Linear issues in the background at a configurable interval (default: 30 seconds). When an issue reaches the configured done status (default: "Done"), QA Hub automatically:

1. Marks the bug as resolved on the Bugs page
2. Sets retestRequired = true on the associated test case
3. Sends an in-app notification
4. Fires a bug.resolved webhook event

Configure the poll interval and done-status in Settings → Analytics → Linear sync.

Columns

Column	Description
Test case	The test case that failed
Bug ticket	Ticket key with a direct link
Linear status	Live status from the last poll
Run	The test run where the failure was recorded
Environment	Run environment label
Flagged at	Timestamp when the bug was linked

In-app notifications

The bell icon in the top bar lights up when a bug is resolved. Click the notification to jump directly to the affected test case in the retest queue.

Jira bug tracking

Jira bug tickets are linked by URL or key. Status is not polled automatically — update the result manually or re-run the test after the fix is deployed.