Skip to main content

​
At a glance

When a test failure is marked as a bug in Checksum, a ticket is created in the connected tracker. Status changes on either side, in Checksum or in the tracker, are reflected back to the other according to your status mappings.
Tickets, not chat alertsIssue Tracker Sync is separate from notification connectors, which post one-way messages to Slack, Teams, Discord, or Google Chat. Issue Tracker Sync creates and manages real tickets in a project tracker.
▦
In the Checksum web app
Connect a tracker and map statuses in Settings → Integrations

​
Connect a tracker

Issue Tracker Sync is configured under Settings → Integrations in the Checksum web app, in its own section, separate from Notification Connectors.
Admin role requiredThe workspace admin role is required to add, edit, or remove connections.
1

Connect a tracker

Find the tracker you want to connect and start the authorization flow. You’re redirected to that provider’s OAuth consent screen. Approve the requested permissions so Checksum can create and update issues on your behalf.
2

Choose the destination

After authorization, select where tickets for this Checksum application should be created: the Jira project, Linear team, or ClickUp list.
3

Configure status mappings

Map each Checksum bug status to a status in the tracker, and choose a sync direction for each mapping. Use auto-map to get suggestions, then review them before saving.
4

Done

The connection is active. The next time a test failure is marked as a bug for that application, Checksum opens a ticket in the destination and starts syncing status changes according to your mappings.
One connection maps a single Checksum application to one destination in one tracker. You can add several connections, for example a Jira project for one application and a Linear team for another.

​
Status mappings

Status mappings control which status changes cross between Checksum and the tracker, and in which direction. You can change them at any time from the connection’s settings panel.

​
Sync direction

Each status pair has its own direction: A common pattern is to map Open → In Progress as Both, so your team can work the ticket from either side, and Done → Resolved as Inbound only, so the tracker is the source of truth for closing it.

​
Auto-map

Auto-map inspects the statuses in the connected tracker destination and suggests pairings by status category. For example, “done” categories map to Checksum’s resolved status. Treat the suggestions as a starting point: not every tracker status has a direct equivalent, so adjust any mapping before saving.
Unmapped statuses are skippedIf a bug or ticket moves to a status with no mapping, nothing is propagated to the other side.
i
How it works
What syncs in each direction, and troubleshooting

​
What syncs

​
Outbound: Checksum → tracker

When a test failure is marked as a bug in Checksum, a ticket is created in the connected destination. Each ticket includes:
  • A title derived from the bug
  • The bug’s description
  • The bug’s severity
  • A deep link back to the bug in the Checksum web app
When the bug’s status changes in Checksum and an outbound mapping exists for that status, the ticket is transitioned in the tracker. Each bug is linked to at most one ticket per connection, so duplicate tickets are never created.

​
Inbound: tracker → Checksum

When a ticket’s status changes in the tracker, the provider sends a webhook to Checksum. Checksum verifies the payload signature (HMAC), finds the linked bug, and updates its status if an inbound mapping exists for that change.
OAuth tokens are stored securely by Checksum and refreshed automatically. They’re never displayed back to you after the initial authorization.

​
Troubleshooting

The test failure wasn’t marked as a bug in Checksum, or no connection is configured for that application.
The status that changed has no outbound mapping, or its direction is set to Inbound only.
The mapping’s direction is set to Outbound only, or the provider’s webhook isn’t configured or lacks permissions.
The OAuth authorization may have been revoked in the tracker. Reconnect from Settings → Integrations to authorize again.
All sync for that destination stops from then on. Tickets already created in the tracker aren’t deleted.

Feature Health Dashboard

Triage bugs and follow their status workflow.

Notifications & Slack

One-way chat alerts for bugs, runs, generation, and healing.