Integrations

Connect test-lab to your issue tracker and file a ticket straight from a run, either by hand from the report or automatically when a run fails.

How it works

• Connect once per account. An owner or admin adds the credentials for a tool in Settings > Integrations. Credentials are encrypted at rest and only decrypted server-side to call the provider. Picking the account-level destination (team / project / repo / list) sets the default for the whole account.
• Route per project. On a project's settings page, the Integrations section can override the destination for that project, or inherit the account default. This is also where you turn on auto-filing.
• File an issue. Any run report has a Create issue action (the report's Issues card). Members can file; only an owner or admin can connect or disconnect a tool.
• Auto-file on failure. When a project opts in, a failing run files an issue automatically into that project's destination. It is deduped per test plan, environment, and device, so a flapping test files one ticket per failure streak, not one per run; a genuine pass clears it so the next failure files again.

Set up a tool

Each tool needs a credential you create on its side, then paste into the connect form. Pick the one you use for what to create, which scopes to grant, and where issues go:

• GitHub Issues
• GitLab Issues
• Linear
• Jira
• Asana
• Trello
• ClickUp