Skip to main content

Connectors

Open Settings → Connectors to configure external issue trackers. A connection holds a workspace credential; a target tells the selected project where to file issues. Connecting a provider does not automatically choose a target for every project.

Connect an issue tracker and choose where the project files issues.

Review the drafted failure report before creating the Jira issue.

Connect and select a target​

  1. Select Configure on the provider card.
  2. Enter the connection details and select Connect.
  3. Choose the project's repository or issue-tracker project and, where offered, the issue type.
  4. Use the connection check to confirm access. A test-issue action creates a real issue; use it only when that is intended.

Supported issue providers are GitHub, Jira, GitLab, and Azure DevOps. GitHub uses the TestVibe GitHub App. Jira needs the site URL, account email, and API token; GitLab needs its URL and an API-scoped token; Azure DevOps needs the organization and a token with Work Items access. Source-code and test-file sync permissions are separate requirements; configure those under Settings → Repositories.

Credentials are encrypted and write-only. A saved connection badge is not proof that every project target is accessible; check the current connection and target when filing fails.

File an issue​

Run, load-run, and generation details offer issue actions for configured trackers. Review the proposed title and body before creating the issue. The issue links back to the relevant TestVibe record and describes captured evidence; it does not upload the artifact files themselves.

An Automation can create an issue after a failed run. Automatic filing uses the failure signature to comment on an existing matching issue instead of creating duplicates. Explicit manual filing does not silently deduplicate.

Chat connectors and notifications​

Slack and Mattermost can appear as chat-capable connector records, but this connector path has no delivery action. Do not treat a saved chat connector as an active notification destination. Automatic completion notifications are email-only. Explicit sharing actions and plugin steps, where available, are separate operations.