> For the complete documentation index, see [llms.txt](https://docs.hackenproof.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hackenproof.com/welcome/integrations/gitlab-issue.md).

# GitLab Issue

## How the connection HackenProof -> GitLab issue works <a href="#h_ed44c51bfe" id="h_ed44c51bfe"></a>

This guide explains how GitLab connection helps companies when they run a bounty program at HackenProof.

Once you connect your bug bounty program to your GitLab repository (public or private), you can automatically create a GitLab issue:

<mark style="background-color:purple;">remember, you can create a GitLab issue for reports with any STATUS</mark>&#x20;

### How to create a GitLab issue <a href="#h_ed44c51bfe" id="h_ed44c51bfe"></a>

* Open the report you want to create a GitLab issue from
* Navigate to the prerequisites section of the report and find the GitLab issue section

<figure><img src="/files/USlKRIR3CJuSlSWx5NYL" alt=""><figcaption></figcaption></figure>

* Press the Create GitLab issue button. As a result, the appropriate issue will be created in your GitLab repository.
* Also, in the report's GitLab section, you will find the link to the newly created issue:

<figure><img src="/files/NldlG5see3Iw2r37ispk" alt=""><figcaption></figcaption></figure>

### How to connect the GitLab repository to the HackenProof program <a href="#h_ed44c51bfe" id="h_ed44c51bfe"></a>

* Open your HackenProof program, which you want to connect to HackenProof
* Navigate to the Integrations tab and open GitLab app

<figure><img src="/files/sxrLl5sTNE97D9u5lmsx" alt=""><figcaption></figcaption></figure>

* Connect your HackenProof program to GitLab by specifying the Repository URL and your GitLab API token.

<figure><img src="/files/aTi2ZuhF81NrDCVwjflO" alt=""><figcaption></figcaption></figure>

**Repository URL.** Be sure you use the correct Project ID (not name). Here is a correct sample: <mark style="background-color:purple;"><https://gitlab.com/api/v4/projects/19980000/issues></mark>, where:

* <https://gitlab.com/api/v4/projects/> - core of our integration
* 19980000 - project ID (not a name)
* *issues* - repo issue page

**GitLab API token.** To create your token: GitLab Project Settings -> Access Tokens&#x20;

<figure><img src="/files/Lhj8Beh2WgyVJzrGUECT" alt=""><figcaption></figcaption></figure>

* Generate personal access token.&#x20;

<mark style="background-color:purple;">Make sure to copy your personal access token now. You won’t be able to see it again!</mark>

Once you specified Project URL and your GitLab token you can connect your bug bounty program with GitLab and start creating GitLab issues


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hackenproof.com/welcome/integrations/gitlab-issue.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.