Connect GitLab
You will learn how to connect GitLab.com, sync projects, map them to Tixio projects, check webhook health, and auto-transition issues when a merge request merges.
Only workspace owners and admins can connect GitLab or change project mappings. Tixio currently supports GitLab.com through this settings flow (not self-managed GitLab hosts in the product UI).
1. Open GitLab settings
- Open your workspace.
- Choose Settings > Integrations.
- Open the GitLab tile.
If the page says GitLab is not configured on this deployment, ask your Tixio administrator to enable the GitLab integration for your environment.
2. Connect GitLab.com
- Choose Connect GitLab.
- Complete the GitLab OAuth authorization.
- Confirm the page shows Connected as your GitLab name and
@username.
Use View on GitLab to open your GitLab account, or Disconnect when you need to remove the connection.
3. Sync and map projects
Under Projects:
- Choose Sync projects to fetch accessible GitLab projects and register webhooks.
- Map each GitLab project to a Tixio project, or leave — Not mapped —.
- Check webhook health on each row:
- Webhook active — deliveries can reach Tixio.
- Webhook not registered — choose Sync projects again after fixing GitLab access.
The header summarizes Last synced time and how many webhooks are active.
4. Configure auto-transition on MR merge
Under Auto-transition on MR merge, enable or disable the setting per Tixio project.
When enabled, merging a merge request that references an issue key (for example
PROJ-123) moves that issue into the project's first completed status.
5. Link development activity to issues
Open an issue Development section. Auto-linking works the same way as GitHub: put the issue key in the MR title, branch name, or commit message, or paste a GitLab MR URL with Link PR.
CI and link state appear alongside GitHub links when both integrations are in use.
What members see without admin access
Members who are not owners or admins cannot change GitLab settings. They can still view linked merge requests, commits, and branches on issues after an admin connects GitLab.
Next
- Connect GitHub if part of the team still uses GitHub.
- Use automation rules for PR merged and Commit pushed triggers.
- Manage webhooks for custom HTTP subscriptions beyond GitLab's built-in sync.