-
Using Unito
-
Items in Sync, Account Management, and Billing
-
Integration Documentation
- Airtable
- Asana
- Azure DevOps
- Basecamp
- Bitbucket
- ClickUp
- Favro
- GitHub
- GitLab
- Google Calendar
- Google Contacts
- Google Sheets
- HubSpot
- Intercom
- Jira
- Mailchimp
- MeisterTask
- Microsoft Excel
- Microsoft Outlook
- Miro
- monday.com
- Notion
- Pipedrive
- Salesforce
- Slack
- Smartsheet
- Teamwork
- Trello
- Wrike
- Zendesk
- Zoho Projects
-
Troubleshooting and FAQs
-
Unito's Trello Power-Ups
-
Data Privacy & Security
Limitations of Unito's GitLab Integration
Here's a breakdown of what Unito's GitLab integration can't do yet — and a few other considerations.
Unito's GitLab integration is designed to get crucial data out of your projects and into other tools. You've seen what Unito can do for GitLab users, so this article will cover what it can't do — yet.
What this article covers:
Unsupported fields
-
Syncing GitLab labels to status fields: While GitLab labels are often used to indicate status in GitLab, they can't be mapped to status fields in other tools. Instead, you should try mapping them to a multi-select dropdown field in your other tool.
-
Syncing merge requests: Merge request statuses also can't be synced.
- Merge request status.
-
GitLab groups: Not currently supported.
-
GitLab subgroups
Other GitLab limitations
- On-premise limitations: If your GitLab installation is using an old database — like a version of MySQL older than 8.0 — you won't be able to sync a description footer to work items in GitLab.