Integrations and External Issues Best Practices
1 min read
Integrations help QA and engineering collaborate while keeping Hawzu as the testing record.
Scope Integrations Deliberately
Section titled “Scope Integrations Deliberately”Use All Projects only when the same external tool and destination should be available across the workspace.
Use Selected Projects when teams use different Jira projects, repositories, Linear teams, Slack channels, or work item destinations.
Keep Credentials Healthy
Section titled “Keep Credentials Healthy”- Use dedicated external credentials where possible.
- Rotate credentials when ownership changes.
- Test the connection after changing credentials.
- Revoke or replace credentials that may be exposed.
Masked fields in the edit flow mean existing sensitive values are kept unless you enter a replacement.
Configure Issue Defaults Carefully
Section titled “Configure Issue Defaults Carefully”Issue creation defaults should route Hawzu defects to the right external destination:
- Jira project and issue type.
- GitHub repository and labels.
- GitLab project and labels.
- Azure DevOps project and work item type.
- Linear team and optional state.
Review defaults when teams reorganize.
Use Slack Notifications Selectively
Section titled “Use Slack Notifications Selectively”Start with defect creation and status update notifications. Turn on optional notifications only when the channel needs that detail.
Too many notifications can hide important signals.
Avoid Two-Way Sync Assumptions
Section titled “Avoid Two-Way Sync Assumptions”Hawzu can create, link, show, open, and unlink external issue references where supported by the visible UI.
Do not assume external tools overwrite Hawzu data or that every field mirrors automatically.