#Integrations Overview
Integrations in Hawzu allow you to connect your test management workflows with the tools your engineering teams already use—without compromising clarity, ownership, or data safety.
Hawzu integrations are designed to add context, visibility, and traceability, not to blur responsibilities between systems.
#Supported Integrations
Hawzu currently supports integrations with:
- Jira – Sync and link defects and test cases with Jira issues
- GitHub Issues – Track issues directly from GitHub
- GitLab Issues – Link and monitor issues and merge-related workflows
- Azure DevOps – Connect work items and test-related artifacts
- Linear – Create and link issues with Linear
- Slack – Receive notifications for executions, defects, and events
Each integration can be configured independently and scoped based on your workspace needs.
#Integration Scope
When adding an integration, you can choose its scope:
This allows teams to:
- Use different tools for different projects
- Gradually roll out integrations
- Avoid unnecessary noise in unrelated projects
#How Hawzu and External Systems Work Together
Hawzu integrations are intentionally designed with clear responsibility boundaries.
#Hawzu focuses on:
- Test case management
- Test execution and results
- Defect tracking
- QA workflows and traceability
#External systems focus on:
- Engineering backlogs
- Development workflows
- Delivery and deployment tracking
Because of this separation:
- Hawzu does not overwrite data in external systems
- External tools do not override Hawzu data
- No silent or automatic two-way sync occurs
- All links are explicit and user-driven
This ensures:
- Predictable behavior
- No accidental data loss
- No sync conflicts
- Clear ownership of information
#Multiple External Links per Defect
A single defect in Hawzu can be linked to multiple external entities, such as:
- Multiple Jira issues
- A combination of Jira, GitHub, and Azure DevOps items
- Different issues representing investigation, fix, and verification work
Each external link:
- Is tracked independently
- Displays its current status and metadata
- Can be opened directly in the external system
- Can be removed without affecting other links
This is especially useful for:
- Cross-team collaboration
- Multi-repo fixes
- Complex defect lifecycles
#Configuration and Management
From the Integrations page, you can:
- Add new integrations
- Edit integration configuration
- Change project scope
- Disable or remove integrations
Each integration maintains its own configuration and authentication details.
#Best Practices
-
Use integrations for context, not control
Keep QA decisions in Hawzu and engineering decisions in external tools.
-
Limit scope where possible
Apply integrations only to relevant projects to reduce noise.
-
Use descriptive integration names
Especially useful when connecting the same tool multiple times.
-
Review integrations periodically
Remove unused or outdated connections to keep your workspace clean.
#What’s Next