Integrations

Spedy connects with the tools your team already uses, so you can keep your code, project management, and time tracking in sync without switching between apps.

Supported Integrations

Connecting a Git Provider

Link your GitHub or Bitbucket account to Spedy so that code activity shows up on your tickets automatically.

GitHub

1. Go to Settings and open the Integrations page
2. Click Add Integration and choose GitHub
3. Authorize Spedy to access your repositories through the secure login flow
4. Once connected, your integration is active and ready to use

Bitbucket

Bitbucket uses Atlassian API tokens with scopes for authentication (Atlassian has retired the legacy App Passwords).

1. Go to id.atlassian.com and create an API token with scopes -- make sure you pick the scoped option, not the legacy scopeless format
2. Select the Bitbucket workspace you want to connect
3. Grant the following scopes:
   • Read: read:repository:bitbucket, read:webhook:bitbucket, read:user:bitbucket, read:pullrequest:bitbucket, read:workspace:bitbucket
   • Write: write:repository:bitbucket, write:webhook:bitbucket, write:pullrequest:bitbucket
   • Delete: delete:webhook:bitbucket
4. In Spedy, go to Settings → Integrations, click Add Integration, and choose Bitbucket
5. Enter your Atlassian account email (not your Bitbucket username) and paste the API token
6. Once validated, your integration is active

If your token is missing a required scope, Spedy shows which scopes are needed so you can fix it without guessing.

Linking commits to tickets

When a team member includes a ticket ID in their commit message -- for example, fix: resolve login timeout CS-42 -- Spedy automatically detects the reference and links the commit to the ticket. The ticket's assignee receives a notification, and the commit appears in the ticket's activity feed.

This works with any commit message that contains a ticket ID, so your team doesn't need to change how they write commits.

Managing your connection

You can disconnect and reconnect an integration at any time from the settings page. If your credentials expire, Spedy will let you know and guide you through reconnecting without losing your configuration.

Importing from Jira

If you're moving from Jira to Spedy, the built-in migration tool makes it easy to bring your existing projects along.

How to migrate a Jira project

1. Go to Settings and open the Integrations page
2. Click Add Integration and choose Jira
3. Enter your Jira site address and an access token to connect
4. Select the Jira project you want to import
5. Spedy automatically maps your Jira statuses, issue types, and priorities to their Spedy equivalents
6. Start the migration -- your tickets, comments, attachments, and assignments are imported automatically

During the migration

You can monitor the progress of your migration in real time. If something goes wrong (for example, a network interruption), the migration can be paused and resumed from where it left off. A detailed log tracks every imported item, so you can verify that everything transferred correctly.

Importing from YouTrack

If you are moving from YouTrack, Spedy offers a similar migration experience to the Jira import.

How to migrate a YouTrack project

1. Go to Settings and open the Integrations page
2. Click Add Integration and choose YouTrack
3. Enter your YouTrack URL and an access token to connect
4. Select the project you want to import
5. Spedy maps your YouTrack fields, statuses, and priorities to their Spedy equivalents
6. Start the migration -- tickets, comments, and assignments are imported automatically

You can monitor progress and view a detailed log just like with the Jira import.

MOCO Time Tracking Sync

If your team uses MOCO for time tracking, billing, or invoicing, you can connect it to Spedy so that time entries are synced automatically.

Setting up the MOCO connection

1. Go to Settings and open the Integrations page
2. Click Add Integration and choose MOCO
3. Enter your MOCO API key and instance URL
4. Map your MOCO projects and users to their Spedy equivalents
5. Once connected, time entries logged in Spedy are synced to MOCO

The sync keeps your billing data in MOCO up to date without manual effort. You can manage the user and board mappings from the integration settings page.

GitHub Issues Sync

If you manage issues on GitHub and want to work on them inside Spedy, the GitHub Issues sync creates a live, bidirectional connection between a GitHub repository and a Spedy board. Issues become tickets, status changes flow in both directions, and comments stay in sync.

Sync modes

Setting up GitHub Issues sync

1. Make sure you already have a GitHub integration connected (see Connecting a Git Provider above)
2. Go to Settings → Integrations → GitHub Issues
3. Select a board and click Configure Sync
4. Choose the repository you want to sync
5. Configure the status mapping:
   • Inbound (GitHub → Spedy): Map GitHub issue states (open, closed) and optionally labels to Spedy board statuses
   • Outbound (Spedy → GitHub): Map Spedy board statuses back to GitHub states (open or closed)
6. Optionally configure:
   • Label mapping: Map GitHub labels to Spedy priorities (e.g., bug → High, enhancement → Medium)
   • Filter labels: Only sync issues that have specific labels (leave empty to sync all)
   • Comment sync: Enable or disable bidirectional comment mirroring
   • Polling interval: How often Spedy checks GitHub for changes (5--60 minutes, default 5)
7. Save the configuration -- Spedy immediately polls GitHub and imports matching issues

How the sync works

Inbound (GitHub → Spedy):

• When a new issue is opened on GitHub, Spedy creates a ticket on the connected board with the mapped status and priority
• When an issue is closed or reopened, the ticket status updates accordingly
• When someone comments on a GitHub issue, the comment appears on the Spedy ticket (attributed to the GitHub author)

Outbound (Spedy → GitHub):

• When a ticket's status changes in Spedy to a column mapped to closed, the linked GitHub issue is closed automatically
• When a ticket moves back to an open-mapped status, the GitHub issue is reopened
• Comments added in Spedy are posted to the GitHub issue

Loop prevention: Spedy ignores inbound updates that were triggered by its own outbound sync, so changes don't echo back and forth.

Monitoring the sync

On the sync configuration page you can see:

• Synced tickets count: How many issues are linked between GitHub and Spedy
• Sync status: Whether each ticket is synced, pending, or has errors
• Audit log: A detailed history of every sync event -- useful for debugging if something doesn't sync as expected

You can also trigger a manual refresh at any time to re-poll GitHub for new or changed issues.

Removing the sync

Deleting the sync configuration disconnects all linked tickets. The tickets remain in Spedy but are no longer updated when the GitHub issue changes. You can always set up the sync again later.

Webhooks

Spedy supports outgoing webhooks so you can notify external systems when events happen in your organization. Configure webhook endpoints to receive HTTP callbacks for events such as ticket creation, updates, status changes, and more.

Setting up a webhook

1. Go to Settings and open the Webhooks page
2. Click Create Webhook Endpoint
3. Enter a name, the destination URL, and select which events to subscribe to
4. Copy the signing secret -- Spedy signs every delivery with HMAC-SHA256 so you can verify authenticity

Each delivery is logged and you can inspect the payload and response status for troubleshooting.

Integration Permissions

Setting up and managing integrations requires the integrations:configure permission (included in the Administrators group by default). Once an integration is active, all team members on the connected boards benefit from it automatically -- no individual setup needed.