GitLab
      Back to home
      1. Help Center
      2. Integration Documentation
      3. GitLab

      An Overview of Unito’s GitLab Integration

      Need to include GitLab in your workflow? Here's a list of the fields you can sync, customization options, and more.

      What does this article cover?

      Supported GitLab issue fields in Unito

      Here are the fields you can sync with GitLab and which ones you can use in rules.

      Quick definitions:

        • One-Way: Changes to the GitLab issue field will appear in the other synced field but not vice versa.
        • Two-Way: Changes to either synced field will appear in the other.
        • Rules: This GitLab issue field can be used as a trigger in your rules to filter work items from syncing with Unito.
      GitLab Field One-Way? Two-Way? Rules?
      Assignee ✔ ✔ ✔
      Comment ✔ ✔  
      Created by ✔    
      Description ✔ ✔  
      Due date ✔ ✔  
      Issue ID ✔    
      Issue number ✔    
      Label ✔ ✔ ✔
      Link to issue ✔    
      Milestone ✔ ✔ ✔
      State ✔ ✔  
      Title ✔ ✔  
      Weight ✔ ✔  

      What counts as an item in sync?

      For GitLab, Unito counts every synced issue as an item in sync.

      Customization option: issue number prefixes

      You can also sync GitLab issue numbers as prefixes to task titles in other tools. That means you could have tasks in a tool like Asana that include the GitLab issue number in the title.

      Limitations of Unito's GitLab integration

      We're constantly looking to improve our GitLab integration. With that in mind, here are a few limitations you should be aware of:

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

      • GitLab groups: Not currently supported. Syncing subgroups also isn't possible.

      Necessary permissions

      The GitLab account you use with Unito needs to be a member of the organization that owns the repository that you want to sync. You'll also need push — or read/write — access.

      We use webhooks to improve workflow performance. To create those webhooks, the GitLab account you use with Unito must have Maintainer or Owner-level permissions. That's because we need the Configure project hooks permission.

      You can learn more about GitLab's user permissions here.

      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.