Integrations
BugDrop connects to your existing tools — push annotations as tickets and receive notifications. Integrations are configured per-project from Dashboard → Integrations.
HOW IT LOOKS IN THE APP
Each category has a header showing the connected count, followed by provider rows. Each row shows the provider logo, name, description, and action buttons (Connect when disconnected; Test + Disconnect when connected). Connected providers expand to show an inline config panel.
Linear
Issues and cycles
Jira
Projects and boards
GitHub Issues
Repositories and issues
GitLab Issues
Projects and boards
Slack
Channel messages
Discord
Server webhooks
Microsoft Teams
Channel notifications
ALL PROVIDERS
Issue Trackers & Boards (13)
Notification Channels (3)
PER-MEMBER INTEGRATION SCOPE
Owners can control each team member's access level to every connected integration. This is set via the Manage integration access option in the member row's role dropdown.
Clients and guests
Client and guest members cannot be given Full scope — they are capped at Provider only. Only developers and owners can have Full scope.
INLINE CONFIG PANEL
After connecting a provider, click the ↓ chevron to expand the inline config panel. This is where you set the target project/board/workspace for ticket creation. Config is saved per-project.
Setup required badge
If a provider is connected but not configured, a 'Setup required' badge appears on the card. The config panel auto-opens on the next page load.
AUTH REFRESH & RECONNECT
If a provider token expires while loading integration resources, BugDrop first attempts automatic token refresh (for OAuth providers that support refresh). If refresh fails or is unavailable, BugDrop returns a reconnect-required state and starts OAuth reconnect from the integrations panel.
Step 1: Resource call returns auth-expired response.
Step 2: Backend attempts refresh + automatic retry.
Step 3: If still unauthorized, UI triggers reconnect flow.
Step 4: Previous integration config values are preserved after reconnect.
No silent data loss
Reconnect updates access tokens but keeps existing provider configuration (such as selected team/project/state) unless you explicitly change it.