Connectors
One connection belongs to the workspace and every project picks its own target — a Jira project key or a GitHub repository. Jira connects with a site, an account and an API token; GitHub connects by installing the app, with no token to paste.
A connector lets TestVibe talk to a tool your team already uses — so a failing run can become a Jira ticket without anyone retyping it.
Find them in Settings → Connectors.
Connections and targets
A connector has two halves, and they are scoped differently.
| Half | Scope | What it is |
|---|---|---|
| Connection | Workspace | The credential. Connect Jira once and every project in the workspace can use it. |
| Target | Project | What this project uses it for — which Jira project, or which repository, issues are filed into. |
That split is why connecting a tool does not immediately change anything: a connection with no target in this project has nothing to act on yet.
Credentials are encrypted when saved and never shown again. To change one, reconnect the provider.
What you can connect
| Provider | Can be used for | What you supply |
|---|---|---|
| GitHub | Issues, source, sync | Install the TestVibe GitHub App. No token is stored — access is minted per request. |
| Jira | Issues | Site URL (https://your-domain.atlassian.net), account email, and an API token from id.atlassian.com. |
| GitLab | Issues, source, sync | Base URL and a token with the api scope. |
| Azure DevOps | Issues, source, sync | Organization name and a personal access token with Work Items (Read & Write). |
| Slack | Chat | An incoming webhook URL. |
| Mattermost | Chat | An incoming webhook URL. |
Connect a provider
- Open Settings → Connectors.
- Select Configure on the provider's card.
- Fill in the fields above and select Connect.
- Choose the project's target — the Jira project or repository to file into.
File an issue from a failure
A run fails, the issue is filed straight from it, and AI writes the report — what broke, the likely cause ranked, and the measured number.
Open the run's ⋯ menu and pick the tracker to file into. Every connected tool that can file issues appears there, so a project with both Jira and GitHub connected offers both. The issue is created with the run's context already filled in, so the person who picks it up can see what failed without opening TestVibe first.
The description is written for you from the run. Press Generate with AI in the composer to replace that summary with an analysis instead — what is broken, the most likely cause ranked, where to look and how to verify. It costs credits, so it is a deliberate click rather than something that happens on every filing, and the result is editable before the issue is created.
The issue body links back to the run in TestVibe and names the evidence it captured — screenshots, video, trace. It does not paste the artifact files themselves, because artifact download links expire and a dead link in a ticket is worse than none.
File issues automatically
An automation can file the ticket for you. Under Automations, create one with:
- Trigger — a run event
- Condition — status is failed
- Action — create issue, pointed at the connection and target you want
Automated filing deduplicates by failure signature: tonight's failure comments on the ticket last night's failure opened, rather than filing a near-identical second one. The signature is based on what failed and why, not on the run's id.
Filing by hand does not deduplicate — if you click the button, you meant it.
Current limitations
Slack and Mattermost can be connected and will show as chat connectors, but no
action posts to them yet. Connecting them now costs nothing and prepares the
workspace, but it will not produce messages.
Issues carry links and descriptions rather than uploaded attachments.