Defects and External Issues
1 min read
Issue-tracking integrations connect Hawzu defects with work in external tools. This gives QA and engineering teams traceability without moving ownership of testing work out of Hawzu.
Create External Issues from Defects
Section titled “Create External Issues from Defects”When issue-tracking integrations are configured, Hawzu can create external issues while creating a defect.
Available issue-creation integrations include:
- Jira
- GitHub Issues
- GitLab Issues
- Azure DevOps
- Linear
The external destination uses the defaults configured for the selected integration.
Link Existing External Issues
Section titled “Link Existing External Issues”From a defect details view, users can link existing external issues when a supported integration is available.
The link flow lets users choose an integration, search issues, select one or more issues, and link them to the Hawzu defect.
View External Issue Details
Section titled “View External Issue Details”Linked external issues appear in defect views and defect tables. Depending on the tool and available data, Hawzu can show:
- External issue key or ID
- Title
- Status
- Priority
- Assignee
- Last updated time
- Link to open the external issue
Unlink External Issues
Section titled “Unlink External Issues”Users can remove a Hawzu link to an external issue from the defect details view.
Unlinking removes the Hawzu reference. It does not delete the external issue.
Connection Errors
Section titled “Connection Errors”If Hawzu cannot read external issue details, the defect table can show an integration problem instead of normal issue details. Edit and test the integration connection to restore visibility.
Ownership Boundaries
Section titled “Ownership Boundaries”Hawzu owns the defect record and test traceability. The external tool owns the external issue workflow. Keep status decisions, comments, and ownership clear in the system where that work belongs.