Defects help teams track issues found during testing, connect them to the work that exposed them, and coordinate resolution across QA, engineering, and release owners.
In Hawzu, defects can be created directly in Hawzu or connected to external issue tools. They can also be linked to test cases, executions, test runs, releases, and requirements so teams can understand impact and risk.
The project Defects page is the main working area for triage and updates. From the project view, users can open defect details, create new defects, update fields inline, and manage traceability.
The workspace defect view shows defects across projects. It includes a Project Name column and project links so users can identify where each defect belongs.
Workspace rows open the related project defect view rather than editing the defect directly in place.
The Defects table shows key defect information for scanning and triage:
Users can search, filter, sort, and choose visible columns.
Current visible defect statuses are:
When a defect is closed, it can also have a resolution:
Status and resolution changes are tracked in defect history.
Priority describes urgency:
Severity describes impact:
Priority and severity can be set during creation and updated later by users with edit access.
Defects can be linked to:
Traceability helps users understand where a defect was found, what it affects, and whether it is connected to a broader pattern.
Your role controls what you can do in Defects. Depending on access, you may be able to:
Read-only views may show defect information without update actions.