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.
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.
Why GitLab and the plan drift apart
Your GitLab projects, tied to your work
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 to connect it
For teams that run on GitLab
Which edition includes what
| 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 | ✗ | ✓ | ✗ |
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.