-
Get Started With Unito
-
Using Unito
-
Items in Sync, Account Management, and Billing
-
Troubleshooting and FAQs
-
Data Privacy & Security
-
Integration Documentation
- Airtable
- Azure DevOps
- Basecamp
- Bitbucket
- ClickUp
- Confluence
- Eloqua
- Favro
- GitLab
- Google Ads
- HubSpot
- Intercom
- Jotform
- Mailchimp
- MeisterTask
- Microsoft Excel
- Microsoft Outlook
- Miro
- monday.com
- Notion
- Pipedrive
- PostgreSQL
- ServiceNow
- Slack
- Snowflake
- Stripe
- SurveyMonkey
- Teamwork
- Typeform
- Xero
- Zendesk
- Zoho Projects
- MySQL
-
Atlassian Jira Integration Docs
-
Trello Power-Up Docs
-
2-Way ServiceNow Integration
-
Asana Integration Docs
-
Flows, Features and FAQs
-
Google Integration Docs
-
Salesforce Integration Docs
-
Wrike Integration Docs
-
Azure DevOps Integration Docs
-
Smartsheet Integration Docs
-
GitHub Integration Docs
Unsupported Features: GitLab
Here's a breakdown of what Unito's GitLab integration can't do yet and a few other considerations.
In this article:
Unsupported GitLab fields
- Merge request: These can't be synced by this integration.
- Epics: Unito can't sync these from GitLab.
- Designs: These can't be synced from GitLab.
-
Merge request status: This field can't be synced.
-
GitLab groups: Not currently supported.
-
GitLab subgroups: Not supported.
Other GitLab limitations
-
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. They can only be mapped to other multi-select dropdown fields.
- Edited comments: When you edit comments in GitLab, these edits won't be synced over to other projects or other tools. That's because Unito only syncs new comments, not any edits to existing comments.
Other GitLab considerations
- 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.