Error Tracking

Overview

Error tracking integrations allow you to automatically create Shortcut Stories when your applications encounter errors, crashes, or exceptions. This ensures bugs are captured immediately and can be prioritized alongside your other development work.

Available Integrations

Common Setup Pattern

Most error tracking integrations follow the same basic setup:

Step 1: Generate a Shortcut API Token

1. Go to Settings > Account > API Tokens in Shortcut
2. Click Generate Token
3. Name it descriptively (e.g., “Sentry Integration”)
4. Copy the token securely

Step 2: Configure in Your Error Tracking Tool

Navigate to the integrations/settings section in your error tracking tool and add the Shortcut API token.

Step 3: Map Projects and Configure Automation

Most integrations allow you to:

• Map error tracking projects to Shortcut Teams/Projects
• Set default Story type (usually Bug)
• Configure automatic Story creation rules
• Set default workflow state and labels

---

Integration Setup Guides

Sentry

Sentry is an open-source error tracking tool that helps developers monitor and fix crashes in real time. The Sentry integration supports bi-directional sync.

Features:

• Create new Shortcut Stories from Sentry issues
• Link Sentry issues to existing Stories
• Auto-complete Sentry issues when Stories reach Done state

Setup:

1. In Shortcut, go to Settings > Integrations > Sentry and enable the integration
2. Click the Sentry account link to open Sentry
3. In Sentry, go to Settings > Integrations, find Shortcut, and click Install
4. Grant the required permissions (Shortcut → Sentry and Sentry → Shortcut)
5. Configure default Project, Custom Field, and Requester for each Sentry project

Sentry Documentation →

---

Bugsnag

Bugsnag provides error monitoring for mobile, web, and server applications.

Setup:

1. Generate a Shortcut API token (see Step 1 above)
2. Copy your Shortcut Project ID from the Project settings
3. In Bugsnag, go to Project Settings > Configure Integrations > Available Integrations
4. Select Shortcut and enter your API token
5. Enable auto-creation in Automation settings if desired

Bugsnag Documentation →

---

Rollbar

Rollbar provides error monitoring, alerting, and analytics for software teams.

Setup:

1. Generate a Shortcut API token
2. In Rollbar, go to User Settings > Connected Accounts > Shortcut tab
3. Enter your API token and save
4. Go to Projects > [Your Project] > Notifications
5. Configure the Shortcut channel with your Workspace name
6. Set Project, Epic, State, and Label defaults
7. Optionally, create Rules for automated Story creation

Note: Workspace name must match your Shortcut URL exactly (case-sensitive, no spaces).

Rollbar Documentation →

---

Honeybadger

Honeybadger provides exception monitoring for Ruby, Python, PHP, and JavaScript applications.

Setup:

1. Generate a Shortcut API token
2. In Honeybadger, go to Settings > Integrations
3. Find Shortcut and click Configure
4. Enter your API token and Workspace slug
5. Configure default Project and Story type

Honeybadger Documentation →

---

Bugsee

Bugsee captures video, network logs, and console output for mobile and web applications.

Setup:

1. Generate a Shortcut API token
2. In Bugsee, go to Settings > Integrations
3. Add Shortcut integration with your API token
4. Configure project mapping and automation rules

Bugsee Documentation →

---

Instabug

Instabug provides bug reporting and crash analytics for mobile applications.

Setup:

1. Generate a Shortcut API token
2. In Instabug dashboard, go to Settings > Integrations
3. Select Shortcut and enter your API token
4. Map Instabug projects to Shortcut Teams/Projects

Instabug Documentation →

---

Additional Integrations

The following integrations are available through the Shortcut Integrations page:

---

Best Practices

Story Configuration

• Use Bug type - Configure integrations to create Stories as Bug type
• Add labels - Use labels like “error-tracking” or the tool name for filtering
• Set priority - Map error severity to Shortcut priority when possible
• Include context - Ensure error details, stack traces, and user info are included

Workflow Automation

• Auto-create selectively - Only auto-create Stories for errors above a threshold
• Deduplicate - Most tools group similar errors; avoid creating duplicate Stories
• Link existing Stories - Before creating new Stories, check if related work exists

Team Practices

• Triage regularly - Review error-created Stories in daily standups
• Close the loop - When fixing bugs, update both Shortcut and the error tracker
• Monitor trends - Use error counts to identify systemic issues