Integrations matrix
A reference table of BugBrain's integration providers — Jira, Linear, Slack, Teams, Email, GitHub Issues, GitLab Issues, Azure DevOps, Asana, and ClickUp — with their type, connect method, and what each is used for.
BugBrain pushes the bugs it finds into your issue tracker and sends run and issue notifications to your team's channels. This page is the provider reference. For setup, see Integrations.
Providers#
| Provider | Type | Connect method | What it's used for |
|---|---|---|---|
| Jira | Issue tracker | API credential | Create issues from found bugs |
| Linear | Issue tracker | API credential | Create issues from found bugs |
| GitHub Issues | Issue tracker | API credential | Create issues from found bugs |
| GitLab Issues | Issue tracker | API credential | Create issues from found bugs |
| Azure DevOps | Issue tracker | API credential | Create work items from found bugs |
| Asana | Issue tracker | API credential | Create tasks from found bugs |
| ClickUp | Issue tracker | API credential | Create tasks from found bugs |
| Slack | Notifier | Webhook URL / connect flow | Send run & issue notifications |
| Microsoft Teams | Notifier | Webhook URL | Send run & issue notifications |
| Notifier | Email address | Send run & issue notifications |
Connect method varies by provider
The exact connect step differs per provider (an OAuth-style connect flow, an API token, or an incoming webhook URL) and is presented in the connect screen for each one. Follow the in-app prompt for the provider you're adding.
Availability: the three gates#
An integration is available to connect only when:
- Feature flag — the provider's
integration.<key>flag is on (the platform kill-switch / rollout control). - Plan matrix — the provider is in your plan's allowed set, or
- Per-workspace grant — it has been granted to your workspace individually, beyond what the plan includes.
In short: available = flag on AND (allowed by plan OR granted to your workspace).
Connecting an integration additionally requires active billing.
Grandfathering
The gates fire on connect and edit only. An integration you've already connected keeps pushing even if your plan later changes — the push path re-checks just the kill-switch flag, never the plan matrix.
All outbound calls from integration providers pass through a server-side safety check before they leave BugBrain.
Related#
Frequently asked questions
Which integrations does BugBrain support?
Ten providers — Jira, Linear, Slack, Microsoft Teams, Email, GitHub Issues, GitLab Issues, Azure DevOps, Asana, and ClickUp. Some are issue trackers (BugBrain files bugs in them) and some are notifiers (BugBrain sends alerts to them).
What decides whether an integration is available to connect?
A three-gate check — the integration's feature flag must be on, the provider must be allowed by your plan's matrix, or granted to your workspace individually. Connecting also requires active billing.
What's the difference between an issue tracker and a notifier?
An issue tracker (like Jira or Linear) is where BugBrain creates issues from the bugs it finds. A notifier (like Slack or Teams) is where BugBrain sends run and issue notifications. Some providers can do both.
Will an already-connected integration stop working if my plan changes?
No. The availability gates fire when you connect or edit an integration, not on every push. Already-connected integrations keep delivering — only the integration's kill-switch feature flag is re-checked on the push path.