Basic Configuration

Settings -> Marketplace Apps -> GitLab integration for Jira

Alternative configuration localizations

Company-managed spaces

Manage your organization's Marketplace and third-party apps

Team-managed spaces

Manage Atlassian Marketplace apps in team-managed spaces

1

Connect your GitLab account

Use GitLab OAuth or Personal Access Token (PAT)

Each connected GitLab account is scoped to an individual Jira administrator and is not shared across users. Jira users must connect their own accounts.

2

Set Up Repository Access

Option 1: Users inherit all repository access from their GitHub account

Per-project repository mapping is not required. Jira users can see the repositories they have access to in GitLab. You can still set Default Repositories, if you do so, users will see the preselected repositories on the work item, but they can change them freely.

Option 2: Users inherit GitHub repository access for selected repositories only

Per-project repository mapping is required. Jira users can see the repositories they have access to in GitLab, but the list is additionally filtered by Default Repositories, if you do not set that mapping, users will not see anything.

Optional Steps

How to Hide the Default Development Panel in Jira Work Items

Disabling unused development features helps reduce noise.

How To Remove or Edit Access to Development Panel from Jira Work Items

1. Remove the Development Field from Layout

This removes the panel from the issue UI.

Steps:

1. Go to Project Settings → Work Items → Layout

2. Find the “Development” field

3. Remove it from the layout

2. Remove “View Development Tools” Permission

This ensures users cannot see development data even if the field exists.

Steps:

1. Go to Jira Settings → Work Items → Permission Schemes

2. Open your permission scheme

3. Locate “View Development Tools”

4. Click Remove

5. Remove all groups, roles, or users

3. Disconnect Unused Git Integrations

Even with permissions removed, integrations may still attach some data.

​