CI/CD
Run a pipeline from a test run, then import what it produced.
- Jenkins Run a job and import its report.
- GitHub Actions Dispatch a workflow on a branch.
- GitLab CI Run a pipeline on a branch.
Keep your stack. Connect it to your tests.
Hawzu is not asking you to move your pipelines or migrate your issues. Connect the tools your team already uses — run their builds from a test run, see their issue statuses on your defects — and keep test management in one place.
Three jobs, one Integrations page
Every integration is configured once per workspace, then made available to all projects or only the ones that need it.
Issue trackers
File the bug where your engineers already work, and see its state in Hawzu.
- Jira File or link an issue; its status shown on the defect.
- GitHub Issues File or link an issue; its status shown on the defect.
- GitLab Issues File or link an issue; its status shown on the defect.
- Azure DevOps File or link a work item; its status shown on the defect.
- Linear File or link an issue; its status shown on the defect.
Notifications
Tell the team when something they care about changes.
- Slack Defect notifications to a channel.
- Webhooks Signed event deliveries to anything else.
Straight answer on trackers: here is everything that crosses between a Hawzu defect and your tracker — including the one arrow that doesn't exist.
As you file the defect Optional, and only then
The issue is created in the tracker you picked.
Any time Read-only
Link an issue that already exists, on any defect.
When you open the defect Fetched on demand
Its status, priority and assignee — shown beside your fields, never
written over them.
After that Never
Hawzu doesn't write back. Edits you make here stay here — no
surprise changes appearing in your engineers' board.
Two trackers is a choice, not a requirement — Hawzu's own defect tracking is built in.
Set up once, and it stays honest
Most integration pain is not the first connection — it is the month later, when a token expired or someone revoked a repository and nobody was told.
No token to paste for GitHub
GitHub connects through a GitHub App. You pick the repositories on GitHub itself and the permissions come with the install — nothing to generate, copy, or rotate. GitLab offers the same via authorization, or a token where you need a service account.
One connection, the jobs you choose
GitHub and GitLab are each a single integration with capabilities. The same connection can link issues and run pipelines — or just one of the two. Turn a capability off and Hawzu tells you exactly what stops working.
Say which repositories you actually use
The provider decides what Hawzu may see. You decide what it uses — so a test run offers a short, relevant list instead of every repository in the organisation.
It tells you when access goes
If a repository's access is withdrawn on the provider, the integration turns amber and names what went missing, rather than failing silently the next time a run needs it.
Workspace-scoped, secrets stay put
Integrations are configured once per workspace and made available to all projects or only chosen ones. Credentials are never sent back to the browser, and install-managed fields can't be overwritten by an ordinary edit.
Not on the list? Use the API
Any CI system that emits a JUnit, TRX, NUnit, Cucumber, or Allure report can post it to Hawzu with one call — which is how Azure DevOps, CircleCI, and Bitbucket pipelines report in today.
Checking
A check is in flight — when the page opens, or when you press Re-check connection.
Connected
The check passed and every repository you configured is still reachable.
Needs attention
The connection is fine, but repositories it was set up to use are gone from the provider. Hawzu names them.
Disconnected
The check itself failed — credentials rejected, or the provider unreachable.
Amber is its own state on purpose. The integration still works, so calling it disconnected would send someone off to reconnect it — which would fix nothing.
The one worth setting up first
Your pipeline, driven from a test run
Connect Jenkins, GitHub Actions, or GitLab CI and a test run can start the build, watch it, read the report it produced, and map every result to a test case — by its code, so renaming a test doesn't break the link.
See how CI/CD automation works →- 3 CI providers Hawzu can trigger
- 5 report formats parsed automatically
- 0 plugins or SDKs to install
Where integrations show up
A connection is only worth having if it changes something downstream — a build that fills a run, or an issue status that shows on the defect it belongs to.
Connect your first tool
Every feature on every plan. Free for five people, $20 per member after — no credit card.