Integrations are most useful when they make external work visible without creating confusion about ownership. Hawzu should remain the source of truth for testing work, while external tools own their own issue, communication, or delivery workflows.
Use the optional Integration Name and Description fields to explain what each connection is for.
Good examples:
Jira - Payments BugsGitHub Issues - Mobile AppSlack - Defect TriageClear names help teams choose the right connection when multiple integrations use the same tool.
Use All Projects only when the same external tool setup applies across the workspace.
Use Selected Projects when:
Project scope keeps unrelated projects from seeing tools they do not use.
Use Test Connection whenever you add or edit credentials. A successful connection is required before saving a fully configured integration.
Re-test after changing:
Integration credentials are sensitive. Rotate them periodically and update Hawzu before old credentials expire.
When editing an integration, sensitive fields are masked. Leave them blank to keep the existing value, or enter a new value to replace it.
For issue-tracking tools, choose defaults that match the most common defect workflow for the scoped projects.
Review defaults for:
Incorrect defaults can send new external issues to the wrong place.
Start with the default Slack notifications for defect creation and status changes. Add optional notifications only when the channel truly needs them.
Too many notifications can make the channel noisy and reduce trust in important alerts.
Use integrations for visibility and traceability. Avoid assuming external tools and Hawzu mirror every workflow step automatically.
Good integration usage:
Do not rely on integrations as a replacement for clear team ownership.
Periodically review configured integrations for:
Delete integrations that are no longer needed. Deleting a Hawzu integration removes the Hawzu connection but does not delete Hawzu defects or external issues.