Create a defect when an issue needs investigation, ownership, and traceability. Hawzu supports creating defects in Hawzu and creating issues in connected external tools.
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.
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.
The title is required. It must clearly summarize the problem.
The title field includes an AI rewrite action to help improve wording before creation.
The description supports rich text, mentions, and attachments. Use it to explain:
New defects default to:
You can change these values before creating the defect.
The assignee and due date are optional. Use them when ownership or timing is already known.
Use Traceability Links to connect the defect to related work:
Linked items appear on the created defect and help teams understand impact.
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.
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:
Only one defect can be selected as the duplicate relationship.
For external tools:
Hawzu keeps a reference to created external issues so they appear in the defect table and details view.
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.