Integrations connect a Hawzu workspace with external tools that teams already use for issue tracking, communication, and continuous integration. They help teams create external issues from Hawzu defects, link existing external issues, review external status details, send selected Slack notifications, and drive CI/CD pipelines from automated test runs.
Supported Integrations
Section titled “Supported Integrations”Hawzu currently supports:
- Jira — issues
- GitHub — issues and Actions workflows
- GitLab — issues and CI pipelines
- Jenkins — CI jobs
- Azure DevOps — work items
- Slack — notifications
- Linear — issues
Each integration is configured at the workspace level and can be made available to all projects or only selected projects.
Capabilities
Section titled “Capabilities”GitHub and GitLab are each one integration with capabilities, rather than one integration per feature. When you connect either, you choose what it should do under What should this integration do?:
| Provider | Capabilities |
|---|---|
| GitHub | Issues — file defects as GitHub issues and keep their status in step. Actions — run workflows from automated test runs and import their results. |
| GitLab | Issues — file defects as GitLab issues and keep their status in step. Pipelines — run pipelines from automated test runs and import their results. |
At least one capability must be selected. Turning the CI capability off later does not delete anything, but test runs using it report automation as unavailable until it is turned back on.
Repositories in use
Section titled “Repositories in use”GitHub and GitLab integrations also record which repositories or projects the workspace actually uses, so test runs offer a short list instead of everything the provider allows. See Repositories and Projects in Use.
Integrations Page
Section titled “Integrations Page”The workspace Integrations page shows configured connections in a table.
The table can show:
- Integration: the connection name.
- Description: the custom or default description.
- Type: the external tool type.
- Scope: All Projects or selected projects.
- Status: Connected, Needs attention, Checking, or Disconnected.
- Configuration: visible setup details such as project, repository, labels, issue type, team, state, or Slack notification preferences.
- Actions: edit or delete.
If no integrations exist yet, use Add Integration to create the first connection.
Project Scope
Section titled “Project Scope”Each integration can be scoped to:
- All Projects: available across the workspace.
- Selected Projects: available only in chosen projects.
Project scope controls where the integration can be used in Hawzu. Use selected projects when different teams or products use different external tools.
Connection Status
Section titled “Connection Status”Hawzu checks configured integrations and displays their current connection state.
- Connected means the connection check succeeded.
- Needs attention means the connection works, but something configured on top of it does not — most often a repository whose access was withdrawn on the provider.
- Checking means Hawzu is validating the connection.
- Disconnected means the connection check failed.
Use Re-check connection on the row to revalidate immediately after fixing something on the provider side. If a connection fails, edit the integration, update credentials or details, and use Test Connection.
CI/CD Automation
Section titled “CI/CD Automation”Integrations with a CI capability — GitHub Actions, GitLab Pipelines, and Jenkins — let a test run drive a pipeline: Hawzu starts the build, watches it, downloads the report, and maps the results back onto test cases.
Learn more in Automated Test Runs.
Defects and External Issues
Section titled “Defects and External Issues”Issue-tracking integrations support defect workflows. Depending on the configured tool, users can:
- Create external issues while creating a Hawzu defect.
- Link existing external issues to a Hawzu defect.
- View external issue status and metadata from defect views.
- Open the external issue from Hawzu.
- Remove a Hawzu link without deleting the external issue.
Learn more in Defects and External Issues.
Slack Notifications
Section titled “Slack Notifications”Slack integrations send selected defect notifications to a configured Slack channel. Hawzu currently exposes notification preferences for defect creation, status changes, assignee changes, comments, traceability changes, priority changes, and severity changes.
Learn more in Slack Notifications.
Permissions
Section titled “Permissions”Available integration actions depend on workspace access. Users may be able to view configured integrations without being able to add, edit, or delete them.