GitLab integration: import issues and connect repositories
Spedy now supports importing GitLab projects with all issues, comments, and assignments. Plus: connect GitLab repositories to boards so commits and merge requests show up on tickets automatically.

Spedy now supports full GitLab project imports and GitLab repository connections for boards. Teams working with GitLab can migrate their issues to Spedy and track code activity directly on tickets at the same time.
Import GitLab projects
Under Settings → Integrations → GitLab you'll find the new GitLab integration. Once connected, you can import entire GitLab projects as new boards — with all issues, comments, and assignments.
How the import works
The import runs in four steps:
Connect GitLab — Enter your GitLab instance URL and a Personal Access Token with
apiscope. Spedy validates the credentials and shows the connected user. Works with gitlab.com and self-hosted instances.Select project — You see a searchable list of all GitLab projects you can access. Each project shows name, path, description, and open issue count. You can customize the target board name.
Map statuses — GitLab uses two base states: "opened" and "closed". Map them to your Spedy board statuses. Optionally, you can use labels as additional status hints — e.g. map "opened:doing" to a specific status.
Map users — Spedy shows all GitLab project members and automatically suggests matching Spedy users (matched by email). You can adjust any mapping manually. Issues from unmapped users are imported without an assignee.
Once started, the import runs in the background. You see progress in real time — imported, pending, and failed issues at a glance. If interrupted, the migration picks up where it left off.
What gets imported
- Issues — title, description, status, due dates
- Comments — all issue notes with author and timestamp
- Assignments — according to the configured user mapping
- External reference — each ticket links back to the original issue (e.g. GL-42)
- Priority and story points — inferred from existing labels
Migration history
On the GitLab page in integration settings, you can see all past migrations with source, timestamp, status, and imported issue count. You can open each migration individually to view the detailed log.
Connect GitLab repositories to boards
In addition to issue imports, you can now connect GitLab repositories to your boards. Commits and merge requests then show up on linked tickets automatically — in real time via webhooks.
Connect a repository
- Open Board Settings → Integrations
- Click Add Repository and select your active GitLab integration
- Choose the GitLab project — Spedy sets up the webhook automatically
You need at least the Maintainer role in the GitLab project for the webhook to be created.
How linking works
When a commit or merge request contains a ticket ID — like fix: login timeout ACME-42 or Closes ACME-42 — Spedy detects the reference automatically. The commit or MR appears in the ticket's code activity with author, message, branch, and timestamp.
Good to know
- The same repository can be connected to multiple boards at once
- Removing a connection automatically deletes the webhook in GitLab
- Push, merge request, and pipeline events are processed
- Works with both gitlab.com and self-hosted instances
Better together
Import and repository connection complement each other: migrate your issues to Spedy, then connect the same GitLab repository to the new board. You get the full project history in Spedy and see every commit and merge request directly on the ticket — without switching between tools.
More details in the Integrations documentation.
Frequently asked questions
Quick answers to the most common questions about this topic.
What data is imported from GitLab?
Can I import only specific issues?
Does the GitLab integration work with self-hosted instances?
What happens if the migration is interrupted?
How do I link commits and merge requests to tickets?
fix: login timeout ACME-42. Spedy detects the reference automatically and links the commit or MR to the ticket.Keep reading

Pull Requests at a Glance, GitHub Issues in Sync
All PRs and merge requests from GitHub, GitLab and Bitbucket in one place. Plus: bidirectional GitHub Issues sync with Spedy tickets.

From Notion + Linear to One Tool: Migration Guide for Engineering Teams
When the Notion+Linear+Toggl Frankenstein stack gets too much — how to switch to an integrated platform in under 2 weeks. Honest migration guide, no marketing.

SPSX Import, New MCP Tools, and Bitbucket Update
Import Spedy Selection Packages directly into new tickets, use new MCP tools for subtickets and ticket links, get started faster with streamlined onboarding, and connect Bitbucket with Atlassian API tokens.