These docs are in English. If you prefer German, write us at beta@clickprobe.ai.

Issue Tracker Integration

Export ClickProbe bugs as GitHub Issues or GitLab Issues with one click from the bug drawer.

Overview

Each ClickProbe project can be connected to one GitHub or GitLab repository. When you export a bug, ClickProbe creates an issue in that repository carrying the full reproduction context: severity, page URL, ordered reproduction steps, screenshot links, and a deep link back to the ClickProbe bug.

One-way only. v1 does not sync status changes from GitHub/GitLab back to ClickProbe. The link is a pointer — ClickProbe is the source of truth for bug lifecycle.

One tracker per project. You cannot connect multiple repositories to a single project in v1.

GitHub Setup

1. Create a Personal Access Token (fine-grained)

  1. Open GitHub → Settings → Personal access tokens → Fine-grained tokens.
  2. Click Generate new token.
  3. Token name: anything descriptive, e.g. ClickProbe export.
  4. Expiration: choose a value your policy allows (90 days or 1 year is common).
  5. Repository access: select Only select repositories → choose your target repo.
  6. Permissions (expand “Repository permissions”):
    • Issues: Read and Write ← required
    • Metadata: Read-only ← required (auto-selected)
  7. Click Generate token and copy it immediately.

2. Connect in ClickProbe

  1. Open your project → Settings → Issue Tracker (or navigate to /app/projects/{id}/tracker).
  2. Click Connect GitHub.
  3. Enter the Repository in owner/repo format, e.g. acme/my-app.
  4. Paste the token into Personal Access Token.
  5. Click Test connection — a green check confirms the token and repository are valid.
  6. Click Save.

Troubleshooting

ErrorCauseFix
token_invalid — check scopesToken expired or wrongRegenerate the PAT and reconnect.
repo 'acme/web' not foundRepository name mismatch or PAT lacks Issues scopeVerify the repo name. Check the fine-grained PAT includes Issues: Read & Write on that repo.
token_forbidden — check repository permissionsPAT has read-only Issues, or repo is a fork without write accessEdit the PAT → Issues: Read and Write.

GitLab Setup

1. Create a Personal Access Token

  1. Open GitLab → Profile → Access tokens (or your self-hosted equivalent).
  2. Add a new token.
  3. Scopes: select api (the recommended minimum). Alternatively write_repository + read_api covers the needed operations.
  4. Copy the token immediately — it is not shown again.

2. Connect in ClickProbe

  1. Open your project → Settings → Issue Tracker.
  2. Click Connect GitLab.
  3. If using a self-hosted GitLab instance, check Self-hosted GitLab and enter your GitLab host (e.g. gitlab.internal.example.com).
  4. Enter the Repository as group/project (e.g. acme/my-app) or a numeric project ID.
  5. Paste the token.
  6. Click Test connection, then Save.

GitLab self-hosted limitations (v1)

  • host is the root hostname only. A GitLab instance mounted under a path (e.g. example.com/gitlab/) is not supported.
  • TLS is required for non-localhost hosts.

Troubleshooting

ErrorCauseFix
token_invalid — check scopesToken expired or wrong scopeRegenerate with api scope.
project 'acme/web' not foundPath wrong or PAT lacks read accessCheck the path. Ensure api or read_api is included.
token_forbiddenPAT lacks issues write permissionAdd api scope (or write_repository).

Exporting a Bug

  1. Open the Bug Inbox (/app/bugs).
  2. Click a bug row to open the drawer.
  3. Click Export in the action bar.
  4. The bug is exported. The drawer shows the issue link chip (e.g. acme/web#42).
  5. The bug’s status changes to exported.

If the project has no tracker connected, the export returns a 409 error with the message tracker_not_configured. Connect a tracker in the project settings first.

Already-exported bugs

If you click Export on a bug that was already exported, ClickProbe returns the existing issue reference without creating a duplicate.

Bulk Export

From the bug inbox, select multiple bugs using the checkbox column, then use the Bulk actions toolbar. Partial failures (e.g. rate limit on one bug) are reported per-bug in the response — successfully exported bugs move to exported status even if others fail.

Token Rotation

  1. Generate a new token with the same scopes.
  2. Open your project → Settings → Issue Tracker → Edit.
  3. Enter the new token (leave the field blank to keep the existing token unchanged).
  4. Click Test connection, then Save.
  5. Revoke the old token in GitHub/GitLab.

The old token is never displayed after initial setup — only the last 4 characters are shown as a reference.

Webhook Integration

When a bug is exported, ClickProbe fires a bug.exported webhook event if you have a webhook configured. See Webhook Integration for the payload schema.