---
title: "GitLab Issues"
slug: "gitlab"
updated: 2021-04-19T14:59:36Z
published: 2021-04-19T14:59:36Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.nucleussec.com/llms.txt
> Use this file to discover all available pages before exploring further.

# GitLab Issues

## Overview

Nucleus enables you to sync your [Gitlab](https://about.gitlab.com/) data directly from the Gitlab platform into the Nucleus console using an automated connector. The connector uses the APIs provided by Gitlab to seamlessly sync data into various Nucleus projects for use in analysis, triage, automation and reporting. (could work in DevOps focus for source code management data, CI/CD data)

## Establish connection

1. From within your Gitlab account, navigate to **Settings > Access Tokens**.
2. Create a new personal access token, setting an expiration for a while from now and checking the **API** scope checkbox.
3. Copy the new token to a clipboard or note.
4. From within a Nucleus project, navigate to **Project Administration > Connector Setup**.
5. Navigate to the **Issue Trackers** section and click the GitLab icon.
6. In the **Setup GitLab Connector** pop-up modal, enter your GitLab URL, repo path (e.g. admin/nucleus-test), username, token that you copied in the previous step, and any labels you want to include when you create GitLab issues in Nucleus.
7. Click **Save Changes** and wait for the Success message.
8. Click **Verify Connection** and wait for the Success message.
9. Select a default assignee if desired and click **Save Changes** again.
10. Close the pop-up modal and you're done!

## Create a ticket

1. Navigate to the **Vulnerabilities > Active** page.
2. Click on any vulnerability to open the vulnerability details view.
3. Click the **Instances** tab.
4. Select one or more instances of the vulnerability and click **Create Issue**.
5. In the **Create Issue** pop-up modal, select GitLab from the dropdown if it's not already selected, fill out the form, and click the **Submit** button.
6. The issue has now been created in your Nucleus and GitLab instances.

If you have any questions, please contact us through the [support center](https://nucleussec.atlassian.net/servicedesk/customer/portal/3).
