Skip to content
Hawzu Docs

Defects Overview

2 min read

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.

Where Defects Appear

Section titled “Where Defects Appear”

Project Defects

Section titled “Project Defects”

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.

Workspace Defects

Section titled “Workspace Defects”

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.

Defect Table

Section titled “Defect Table”

The Defects table shows key defect information for scanning and triage:

  • Defect Code
  • Title
  • Priority
  • Severity
  • Status
  • Reporter
  • Assignee
  • Due Date
  • Project Name in the workspace view
  • Created Date
  • Last Updated
  • Integrations

Users can search, filter, sort, and choose visible columns.

Lifecycle

Section titled “Lifecycle”

Current visible defect statuses are:

  • New
  • In Progress
  • Resolved
  • Closed
  • Reopened

When a defect is closed, it can also have a resolution:

  • Fixed
  • Duplicate
  • Rejected
  • Deferred
  • Withdrawn

Status and resolution changes are tracked in defect history.

Priority And Severity

Section titled “Priority And Severity”

Priority describes urgency:

  • High
  • Medium
  • Low

Severity describes impact:

  • Blocker
  • Critical
  • Moderate
  • Minor
  • Enhancement

Priority and severity can be set during creation and updated later by users with edit access.

Traceability And Integrations

Section titled “Traceability And Integrations”

Defects can be linked to:

  • Requirements
  • Test cases
  • Executions
  • Test runs
  • Releases
  • External issues
  • Related or duplicate defects

Traceability helps users understand where a defect was found, what it affects, and whether it is connected to a broader pattern.

Permissions

Section titled “Permissions”

Your role controls what you can do in Defects. Depending on access, you may be able to:

  • View defects
  • Create defects
  • Edit defect fields
  • Add comments
  • Update traceability
  • Link external issues
  • Delete defects

Read-only views may show defect information without update actions.

Next Steps

Section titled “Next Steps”