Sentry

Turn issue alerts into bug tickets your team can act on.

An error should arrive where the team plans its work, with enough context to act and none of the sensitive request data that belongs in Sentry. Connect your sentry.io organisation, map each Sentry project to a Cohively board, and an issue-alert action creates one linked bug ticket that stays current on later alerts. When the ticket is done, the issue is resolved in Sentry too, so a fixed bug does not stay open in both tools.

Get started Explore all features

What it looks like

Map the project, then select the Cohively action in a Sentry issue alert rule. Only future triggers create work.

Sentry project   checkout-api
Cohively board  Checkout
Alert action    Create a Cohively bug

How to connect

A few minutes, once. Then it looks after itself.

Connect your organisation

Open Administration → Integrations and choose Connect Sentry. An administrator authorises one sentry.io organisation for the workspace.

Map projects to boards

Choose a Cohively project or the general board for each accessible Sentry project. Leave projects unmapped when they should not create tickets.

Add the alert action

In a Sentry issue alert rule, add the Cohively action. Future triggers create a linked bug or refresh its safe Sentry metadata.

Why teams turn it on

Get started

One issue, one ticket

Webhook retries and repeated alerts never produce duplicate work. The same Sentry issue always points to the same Cohively ticket.
Human decisions stay intact

Later alerts update only the mirrored Sentry facts. Your title, description, status, project, priority, service level, assignee and parent remain untouched.
Useful context without sensitive payloads

Tickets show identifiers, counts, environment, culprit and seen dates. Stack traces, breadcrumbs, requests and user context are never stored.
Clear ownership and history

New bugs use your workspace defaults and appear unassigned and unwatched, while integration-created activity is clearly attributed to Sentry.

The details

Sentry version: Sentry’s hosted sentry.io service. Self-hosted Sentry and pasted API tokens are not supported in this first version.
Permissions requested: Read access to the organisation, projects and issues, plus permission to set an issue’s status — used for nothing but resolving an issue whose ticket is done.
What creates a ticket: Only a future event alert triggered through the Cohively issue-alert action. Existing issues are not imported and resolve or reopen events do not move tickets.
Who can configure it: A workspace administrator with permission to manage settings. One active Sentry organisation can be connected to a workspace.
Disconnecting: Disconnecting or uninstalling stops processing and clears credentials, while project mappings, issue metadata and ticket links remain available as history.