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

# GitLab

{% hint style="info" %}
BugSplat's GitLab integration is in beta. Please message us if you want to request a feature or report a bug.
{% endhint %}

BugSplat allows your team to create issues in [GitLab](https://gitlab.com) with a few clicks. Our integration adds valuable crash data to your GitLab issues and links to the BugSplat dashboard so your team can quickly switch between looking at BugSplat and your GitLab repos.

#### Integrating GitLab and BugSplat

1. Login to your account.
2. Click the Gear icon (⚙️) at the top right of the page and navigate to the [Database Settings](https://app.bugsplat.com/v2/database/integrations) page, and under **Database > Integrations >** **Defect Tracker**, select **GitLab** from the options shown.
3. Enter your GitLab [personal API token](https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html#create-a-personal-access-token) with the API scope into the field labeled **Token.**
4. Click **Update**.
5. Once you have connected to GitLab, you can select one of your projects from the **Projects** dropdown list.
6. After selecting your desired board, click **Update** again.

#### Push a New Item to GitLab

1. Use the **Create Defect** button to create a new item on the crashes page or a crash group page to push a new item to GitLab.
2. Enter relevant details and click the **Submit** button to create the defect.
3. Click the link to view the new GitLab issue created by BugSplat.
4. View the items' updates to see that stack trace and other valuable info from BugSplat.

<figure><img src="https://976110677-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LBMgmIcgkIXSUfnXDSv%2Fuploads%2FsDHHI8WnmgTxgCdiGmRd%2Foutput.gif?alt=media&amp;token=e604ffda-e096-45ad-ae58-cb5a35d80b01" alt=""><figcaption><p>Add BugSplat Item to GitLab</p></figcaption></figure>

#### Automated Defect Creation <a href="#automated-defect-creation" id="automated-defect-creation"></a>

Want to create issues in GitLab automatically for each new crash or crash group? Check out the document on auto-creating defects in your third-party defect tracker tool [here](https://docs.bugsplat.com/introduction/development/integrating-with-tools/issue-trackers/auto-creating-defects-from-bugsplat-databases-in-attached-third-party-trackers).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bugsplat.com/guides/integrating-with-tools/issue-trackers/gitlab.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
