Configure Integrations
1 min read
Each integration is configured individually. You provide the connection details, test the credentials, and pick the defaults Hawzu uses when defects create or sync external issues — or, for a CI provider, which repositories automated test runs may use. Use the guide for the tool you want to connect.
Issue Trackers
Section titled “Issue Trackers”- Jira: connect Jira, test credentials, and set defaults for external issues created from defects.
- Azure DevOps: connect Azure DevOps and choose default work item settings for defects.
- GitHub: install the Hawzu GitHub App, then choose default repositories and labels for external issues.
- GitLab: authorize with GitLab or use a token, then choose default projects and labels for external issues.
- Linear: connect Linear and choose default team and state settings for external issues.
CI/CD Providers
Section titled “CI/CD Providers”- GitHub: enable the Actions capability to run workflows from automated test runs.
- GitLab: enable the Pipelines capability to run pipelines from automated test runs.
- Jenkins: connect a Jenkins instance and run its jobs from automated test runs.
GitHub and GitLab are each one integration whose capabilities you choose, so the same connection can file issues and run CI. See Connect a CI Provider.
Notifications
Section titled “Notifications”- Slack: connect Slack, choose a notification channel, and manage defect notification preferences.
Before You Start
Section titled “Before You Start”You’ll typically need credentials or an access token for the external tool, along with permission to add an integration in the project. GitHub is the exception — it needs no token at all, only permission to install a GitHub App. After connecting, test the credentials before saving so defect sync, issue creation, and pipeline triggering work reliably. For the wider picture, see the Integrations overview.