How it works

Range will add Check-in suggestions for GitLab Issues that are opened, reopened, updated, or closed that are assigned to you, as well as for Merge Requests that you open, merge, or close.

Setup

An administrator with "Owner" access to the GitLab projects you want to track must connect GitLab once for the whole Range workspace on the integrations settings page. When you click "Set this up" for the GitLab integration, you should be redirected to the GitLab and asked to authorize access for Range:

Once you click "Authorize", you should be redirected back to the Range app and individual users can then link their identity from the integrations settings page, which will allow them to receive Check-in suggestions for their activity in GitLab.

Self-managed GitLab Setup

An administrator with admin access to both your GitLab instance and your Range organization must connect it once for the whole Range workspace. First, create an OAuth application for Range in your GitLab instance following the instructions from GitLab, using Range redirect URL (https://range.co/oauth/callback). api and read_user scopes must be enabled for the application.

Once created, you should be presented with an application id and secret which need to be entered for GitLab integration settings in Range, along with your installation's hostname (e.g. "gitlab.your-company.com"). Your Range organization's integration settings are found under Settings > Integrations and GitLab self-managed instance settings are found in advanced configuration for GitLab integration.

Security considerations

When an administrator connects GitLab via OAuth, the api scope is requested and used to list the projects the user has access to, and add webhooks to each of them to notify Range of events. These permissions do not allow access to source code, we only add webhooks to projects that belong to groups, and confidential Issues are ignored.

Individual users must also go through an OAuth flow in order to link their accounts. The only scope requested is read_user and is used to identify the authenticated user so that they can later be matched up with GitLab activity.

Range persists the following data for GitLab Issues:

• Issue ID
• Title
• URL
• Project Name
• Project Description
• Project URL
• Created At
• State

And for Merge Requests:

• Merge request ID
• Title
• Description
• URL
• Project Name
• Project Description
• Project URL
• Created At
• Updated At
• State