Skip to content
Hawzu Docs

Create Defect

2 min read

Create a defect when an issue needs investigation, ownership, and traceability. Hawzu supports creating defects in Hawzu and creating issues in connected external tools.

Open The Create Defect Window

Section titled “Open The Create Defect Window”
  1. Open the project Defects page.
  2. Select Create Defect.
  3. Choose where the defect should be created.
  4. Fill in the required details.
  5. Select Create Defect.

Choose A Destination

Section titled “Choose A Destination”

Hawzu Defect

Section titled “Hawzu Defect”

Choose Hawzu when the defect should be managed inside Hawzu. This keeps the defect, comments, traceability, similar-defect suggestions, history, and notifications in the project.

External Tool

Section titled “External Tool”

Choose External Tool when the issue should be created in one or more connected tools such as Jira, GitHub, GitLab, Azure DevOps, or Linear.

When external tools are selected, Hawzu shows the fields required by the selected tools. Shared title and description values are mapped into matching external fields where available.

Hawzu Defect Fields

Section titled “Hawzu Defect Fields”

Defect Title

Section titled “Defect Title”

The title is required. It must clearly summarize the problem.

The title field includes an AI rewrite action to help improve wording before creation.

Description

Section titled “Description”

The description supports rich text, mentions, and attachments. Use it to explain:

  • What happened
  • How to reproduce it
  • Expected behavior
  • Actual behavior
  • Useful investigation details

Priority And Severity

Section titled “Priority And Severity”

New defects default to:

  • Priority: Medium
  • Severity: Moderate

You can change these values before creating the defect.

Assignee And Due Date

Section titled “Assignee And Due Date”

The assignee and due date are optional. Use them when ownership or timing is already known.

Section titled “Traceability Links”

Use Traceability Links to connect the defect to related work:

  • Requirements
  • Test cases
  • Executions
  • Test runs
  • Releases

Linked items appear on the created defect and help teams understand impact.

Custom Fields

Section titled “Custom Fields”

Active custom fields for defects appear during creation. Required custom fields must be completed before the defect can be created.

Disabled or deprecated custom fields are not shown for new defects.

Similar Defect Suggestions

Section titled “Similar Defect Suggestions”

While you enter the title and description, Hawzu compares the draft against existing defects and shows similar-defect suggestions when enough detail is available.

For each suggestion, you may be able to:

  • Link as related
  • Link as duplicate
  • Close the new defect as a duplicate
  • View solution, reason, or details

Only one defect can be selected as the duplicate relationship.

External Issue Creation

Section titled “External Issue Creation”

For external tools:

  • Select one or more configured integrations.
  • Enter shared issue content.
  • Fill any tool-specific required fields.
  • Submit the defect.

Hawzu keeps a reference to created external issues so they appear in the defect table and details view.

Submit Behavior

Section titled “Submit Behavior”

The Create Defect action is available when the required title is filled in. If required custom fields or external-tool fields are missing, Hawzu asks you to complete them before creating the defect.

Next Steps

Section titled “Next Steps”