GitLab - Jam Documenation

Documentation Index

Fetch the complete documentation index at: /docs/llms.txt

Use this file to discover all available pages before exploring further.

Connect Jam to GitLab so that every bug you capture becomes a GitLab issue with all the technical context engineers need already attached. Stop copying and pasting debug information. Jam handles it automatically.

You need the Jam Chrome extension installed. See Getting Started if you haven’t set it up.

What’s included in every GitLab issue

Every GitLab issue created from Jam automatically includes:

Create a GitLab issue from a new capture

  1. Capture your bug
    Use the Jam browser extension to capture your bug.

  2. Select GitLab as the destination
    In the Jam extension, click Link you can share and change the destination to GitLab.

  3. Authenticate with GitLab
    Complete the GitLab OAuth flow to connect your account.

  4. Configure your GitLab issue
    Once connected, set up your issue from Jam: choose the project, assignee, labels, due date, milestones, and more.

  5. Create the issue
    Click Create issue. Jam creates the GitLab issue and opens it in a new tab.

Click Edit fields during issue setup to manage which GitLab fields appear in the Jam extension. Hide fields you don’t use to keep the workflow fast.

Create a GitLab issue from any Jam you’ve already captured in two clicks.

You must be logged into Jam to use this feature. Logged-out users will not see the Send to App option.

Create a GitLab issue from an existing Jam

  1. Open the Jam
    Open the Jam you want to convert into a GitLab issue.

  2. Click Send to App
    Click Send to App and select GitLab.

  3. Log in to GitLab if prompted
    If this is your first time using Jam + GitLab, you’ll be redirected to authenticate.

  4. Fill in the issue details
    Enter the repository, assignees, labels, milestone, and any other fields you need.

  5. Create the issue
    Click Create issue to send the Jam to GitLab.