Basic Configuration
Last updated
Settings -> Marketplace Apps -> GitLab integration for Jira
Manage your organization's Marketplace and third-party apps

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.
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.
Disabling unused development features helps reduce noise.
How To Remove or Edit Access to Development Panel from Jira Work Items
This removes the panel from the issue UI.
Steps:
Go to Project Settings → Work Items → Layout
Find the “Development” field
Remove it from the layout

This ensures users cannot see development data even if the field exists.
Steps:
Go to Jira Settings → Work Items → Permission Schemes
Open your permission scheme
Locate “View Development Tools”
Click Remove
Remove all groups, roles, or users

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