--- title: "GitLab Integration for Project Management | Orangescrum" description: "Connect GitLab projects to Orangescrum, self-managed included. Issues, comments, and labels sync both ways, and Self-Hosted adds merge requests." canonical: https://www.orangescrum.com/integrations/gitlab --- # GitLab Integration for Project Management | Orangescrum > For the complete documentation index, see [llms.txt](https://www.orangescrum.com/llms.txt). [Home](/) / [Integrations](/integrations) / GitLab GitLab # GitLab Integration, _Including Self-Managed_ Point Orangescrum at gitlab.com or at the GitLab instance running inside your own network. Issues and comments stay in step, and in the Self-Hosted edition your pipeline shows up on the work item. Available in[Cloud](/pricing "Cloud - included")[Self-Hosted](/self-hosted "Self-Hosted - included")Open Source [Start Free Trial →](/sign-up?utm_source=website&utm_medium=feature&utm_content=gitlab)[Book a Demo](https://calendly.com/orangescrum) Issue sync in Cloud and Self-Hosted - the DevOps layer is Self-Hosted ## What does the GitLab integration do? The GitLab integration links a GitLab project to an Orangescrum project so the two stay in step. Issues and tasks sync both ways, comments and labels are carried across, and repository events arrive by webhook with the signature verified. Because the instance URL is part of the configuration, this works against gitlab.com and against a self-managed GitLab equally. In the Self-Hosted edition it extends into delivery: create a branch or a merge request from a work item, see GitLab CI status on the task, and stop a merge until the linked task reaches a status you allow. The problem ## Why GitLab and the plan _drift apart_ Issues and tasks are maintained separately Developers work in GitLab issues, everyone else works in the project tool, and the two versions diverge within a week. ✓ Two way sync means one story, visible in both. Self-managed GitLab gets left out Integrations that only speak to gitlab.com are useless to teams running their own instance behind a firewall. ✓ The instance URL is configurable, so self-managed works the same way. Pipeline results never reach the plan The CI job is red and the board still says the task is done. ✓ GitLab CI status lands on the work item, in Self-Hosted. What you get ## Your GitLab projects, _tied to your work_ Issue and comment sync in both editions, with branches, merge requests, and CI status on top of it in Self-Hosted. - ### Project to project mapping Connect over OAuth and map each GitLab project to the Orangescrum project that owns that work. - ### Self-managed GitLab The instance URL is part of the configuration, so your own GitLab server is connected the same way as gitlab.com. - ### Two way issue sync Issues and tasks stay in step, including closing, with state and priority translated between the two systems. - ### Comment and label sync Comments and labels are carried across, so the discussion and the categorisation are not split between two tools. - ### Verified webhooks Repository events arrive by webhook and the signature is checked, so updates are immediate and trustworthy. - ### Create a branch from a task Start a GitLab branch from the work item, with the task identifier in the name so commits link back on their own. Available in Self-Hosted. - ### Create a merge request from a task Open the merge request from the work item instead of switching tools. Available in Self-Hosted. - ### GitLab CI status and gating See pipeline status on the work item and block a merge until the linked task reaches an allowed status. Available in Self-Hosted. How it works ## How to _connect it_ 1 Register the application in GitLab Create an OAuth application on gitlab.com or on your own instance, with the callback URL Orangescrum gives you. 2 Enter the instance and credentials Supply the GitLab URL, the client id, and the secret. Secrets are encrypted before they are stored. 3 Map projects Point each GitLab project at the Orangescrum project that owns that work, and choose what should sync. 4 Add the delivery layer In Self-Hosted, turn on CI status and set which workflow statuses are allowed to merge. Who it's for ## For teams that _run on GitLab_ Self-managed GitLab shops Organisations running GitLab inside their own network who need the project tool to reach it. [Learn more →](/self-hosted) Software teams Developers who want the board to reflect what is happening in the repository. [Learn more →](/solutions/it-project-management-software) Mixed toolchains Companies running GitLab in one team and GitHub in another. [Learn more →](/integrations) Availability ## Which edition includes _what_ Orangescrum runs as managed cloud, self-hosted on your own servers, or as the open-source Community Edition. Here is exactly what each one includes. Issue and comment sync are in Cloud and Self-Hosted. Branches, merge requests, and CI status are Self-Hosted. | Capability | CloudManaged SaaS | Self-HostedOn-premise / private cloud | Open SourceCommunity Edition | | Project connection and mapping, including self-managed GitLab | ✓ | ✓ | ✗ | | Two way issue and task sync | ✓ | ✓ | ✗ | | Comment sync | ✓ | ✓ | ✗ | | Label sync | ✓ | ✓ | ✗ | | Verified webhook updates | ✓ | ✓ | ✗ | | Read branches, commits, and merge requests | ✓ | ✓ | ✗ | | Create a branch from a work item | ✗ | ✓ | ✗ | | Create a merge request from a work item | ✗ | ✓ | ✗ | | GitLab CI status on the work item and merge gating | ✗ | ✓ | ✗ | Frequently asked questions ## GitLab integration _FAQ_ ### Does Orangescrum integrate with GitLab? Yes. You connect over OAuth, map GitLab projects to Orangescrum projects, and issues, comments, and labels sync both ways. Events arrive by webhook with the signature verified. ### Does it work with self-managed GitLab? Yes. The GitLab instance URL is part of the configuration rather than being hard coded to gitlab.com, so a GitLab server running inside your own network is connected in exactly the same way. If that server is not reachable from the internet, run Orangescrum self-hosted alongside it. ### Which edition includes what? Project connection, issue sync, comment sync, label sync, webhooks, and reading branches, commits, and merge requests are in both Cloud and Self-Hosted. Creating a branch or merge request from a task, GitLab CI status, and merge gating are Self-Hosted only. Nothing here is in the free Community Edition. ### Can I create a merge request from a task? Yes, in the Self-Hosted edition. Both editions can read and list merge requests, but creating one from a work item is part of the self-hosted DevOps layer. ### Does it show GitLab CI pipeline status? Yes, in the Self-Hosted edition. Pipeline events are normalised alongside GitHub Actions, Jenkins, and Bitbucket Pipelines, so mixed toolchains still give one view of build status on the work item. ### How does Orangescrum know which task a branch belongs to? It reads the work item identifier out of branch names, commit messages, and merge request titles, and resolves it against the Orangescrum project mapped to that repository. ### Do issues sync in both directions? Yes. Creating or updating an issue in GitLab updates the linked Orangescrum task, and the reverse is also true, including closing. Priority and state are translated between the two models rather than assumed to match. ### What happens to my credentials? The client id and secret you enter are encrypted before they are stored, and webhook payloads are checked against your webhook secret before they are accepted. ## Connect GitLab to your projects Issue and comment sync are available in Cloud and Self-Hosted. Branches, merge requests, and CI status are part of the Self-Hosted edition. [Start Free Trial →](/sign-up?utm_source=website&utm_medium=feature&utm_content=gitlab_cta)[Book a Demo](https://calendly.com/orangescrum) ## Related capabilities [All integrationsSee everything Orangescrum connects to](/integrations)[GitHub integrationThe same sync for GitHub repositories](/integrations/github)[Jenkins and CI/CDPipeline status on your work items](/integrations/jenkins)[Self-Hosted editionRun Orangescrum on your own servers](/self-hosted)