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.

  • 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.
  • 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.

Got feedback? Submit a Unito feature request to let us know what you'd like to see in the next update to our GitLab integration.