#Defects FAQs - Bug Tracking Questions
This section answers common questions about defect management and bug tracking in Hawzu.
#What is a defect?
A defect is an issue or bug identified during test execution or reported manually.
Defects represent problems that need to be tracked, analyzed, fixed, and verified.
Defects can relate to:
- Functional issues
- Performance problems
- UI/UX issues
- Security or data issues
#How do I create a defect?
You can create a defect in multiple ways:
#From the Defects page
- Navigate to Defects
- Click Create Defect
- Fill in defect details (title, description, priority, severity)
- Optionally link test cases, executions, or releases
- Add attachments if needed
- Click Create
See the Creating Defects guide for details.
#Can I create a defect from a failed test case?
Yes — this is the recommended approach.
When you create a defect from a test case execution:
- Priority and severity are auto-prefilled from the test case
- The release and execution are automatically linked
- Step details up to the failure point are consolidated into the defect description
- Traceability is preserved without manual effort
This ensures accurate context and faster triage.
#What’s the difference between priority and severity?
- Priority: How urgently the defect should be fixed (business impact)
- Severity: How serious the impact is when the defect occurs (technical impact)
Examples:
- High severity + low priority → Rare but critical edge case
- Low severity + high priority → Minor issue blocking a release deadline
#What defect statuses are available?
Defects move through a lifecycle that typically includes:
- New – Defect has been reported
- In Progress – Actively being worked on
- Resolved – Fix implemented, awaiting validation
- In Test – Fix under QA verification
- Verified – Fix confirmed
- Closed – Defect completed
- On Hold – Work paused
- Deferred – Not planned for the current cycle
- Duplicate – Already reported elsewhere
- Rejected – Not a valid defect
- Reopened – Issue persists after fix
Not all workflows use every status, but Hawzu supports flexible lifecycle tracking.
#How do I track defect progress?
You can track defect progress by:
- Viewing status changes in the defect timeline
- Monitoring linked test executions
- Checking release-level defect summaries
- Using Observatory analytics for trends and insights
#Can I link defects to test cases and executions?
Yes.
Defects can be linked to:
- Test cases
- Test executions
- Releases
This enables:
- Full traceability
- Easier verification
- Better reporting and analytics
#How do I know if a defect is fixed?
A defect is typically considered fixed when:
- The developer marks it as Resolved
- QA re-executes the linked test case
- The issue no longer reproduces
- The defect is marked Verified or Closed
Execution-linked defects make this process faster and more reliable.
#Can one defect be linked to multiple executions?
Yes.
A single defect can be linked to multiple executions across:
- Different test runs
- Multiple releases
- Repeated failure scenarios
This helps identify recurring issues and measure defect impact over time.
#What happens if a defect is reopened?
When a defect is reopened:
- Its status moves back to Reopened
- It re-enters the active defect workflow
- Linked executions and history are preserved
This ensures transparency and auditability.
#Still have questions?