Defects

Bugs found during testing — or reported any other way — get tracked here, from first report to closed.

Logging a bug

Create a bug directly from the Bugs screen, or — the more common path — click Report a Bug on a failed execution result, which pre-fills the linked test case, suite, and plan. Every bug gets:

A summary, description, and steps to reproduce.
Severity and priority (Low/Medium/High/Critical, tracked separately — severity is how bad it is, priority is how soon it should be fixed).
An assignee and a reporter.
Links to the test case(s), test suite, and test plan it relates to — a bug can be linked to more than one test case if it affects several.

Bug status

New In Progress Fixed Retest Closed Reopened

A closed bug that resurfaces gets marked Reopened rather than a fresh new bug being filed — keeps its full history (comments, links, original report) attached.

Discussion & evidence

Each bug has threaded comments (replies nest one level under the original) and file attachments — paste a screenshot directly into a comment, or attach a file the same way you would on a test case.

Exporting & seeing the bigger picture

The Bugs list exports to CSV, Excel, or PDF honoring whatever filters you've applied. For a wider view — which combinations of severity and priority your open bugs actually cluster around — see the Severity × Priority Matrix on the Reports page.

Who can do this: most testing roles can create and update bugs on projects they belong to; a couple of roles (Business Analyst, Client) have read-only access.

Next: Reports & Matrices →