Integrations
Connect Spedy to GitHub, GitLab, Bitbucket, Jira, YouTrack, and MOCO to streamline your workflow.
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
| Service | What you can do |
|---|---|
| GitHub | Link commits and branches to tickets, receive updates when code is pushed |
| GitLab | Link commits and branches to tickets, receive updates when code is pushed |
| Bitbucket | Link commits and branches to tickets, receive updates when code is pushed |
| Jira | Import existing Jira projects into Spedy with all tickets, statuses, and assignments |
| YouTrack | Import existing YouTrack projects with tickets, custom fields, and assignments |
| MOCO | Sync time entries between Spedy and MOCO for billing and invoicing |
Connecting a Git Provider
Link your GitHub, GitLab, or Bitbucket account to Spedy so that code activity shows up on your tickets automatically.
How it works
- Go to Settings and open the Integrations page
- Click Add Integration and choose your provider (GitHub, GitLab, or Bitbucket)
- Authorize Spedy to access your repositories through the secure login flow
- Once connected, your integration is active and ready to use
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
- Go to Settings and open the Integrations page
- Click Add Integration and choose Jira
- Enter your Jira site address and an access token to connect
- Select the Jira project you want to import
- Spedy automatically maps your Jira statuses, issue types, and priorities to their Spedy equivalents
- 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
- Go to Settings and open the Integrations page
- Click Add Integration and choose YouTrack
- Enter your YouTrack URL and an access token to connect
- Select the project you want to import
- Spedy maps your YouTrack fields, statuses, and priorities to their Spedy equivalents
- 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
- Go to Settings and open the Integrations page
- Click Add Integration and choose MOCO
- Enter your MOCO API key and instance URL
- Map your MOCO projects and users to their Spedy equivalents
- 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.
Integration Permissions
Setting up and managing integrations requires administrator access. Once an integration is active, all team members on the connected boards benefit from it automatically -- no individual setup needed.