Self-Hosted GitLab
Share complete bug reports as issues directly to your GitLab self-hosted project’s issue boards.
BetterBugs Integration with Your Self-Hosted GitLab Instance
You can integrate BetterBugs.io with your self-hosted instance on GitLab.
Whenever you face an issue in your app, you can instantly capture it using the BetterBugs extension and share it with your GitLab self-hosted instance as an issue.
With every issue raised (created as bug reports using BetterBugs) in your GitLab project, you get:
The visual evidence captured as a screenshot, screen recording, or a 2-minute Rewind video session
Issue description (added manually or AI-generated by the reporter)
Device and environment info when the issue occurred.
Console logs, network requests, and any other logs.
Page navigation steps
Metadata (Custom)
App local and session storage
Your engineers get all this info as a bug report packed with visual evidence and technical details for debugging. You can access the complete bug report with the unique report link included within the GitLab task created as an issue on your self-hosted project.
What Do You Need for the Setup and How it Works?
How to Set Up a New OAuth Application in GitLab (for Self-Hosted instance): Step-by-Step
Add Name, Redirect URI, and Select Scopes
Add details for the app:
Name — Provide a unique name for your application, (e.g., BetterBugs Test App)
Redirect URI — Here, add “
https://app.betterbugs.io/connect/gitlab” as the Redirect URI. (Please use this exact address for any new app(s) you’d want to connect with BetterBugs.)Confidential — It should be ✅auto-checked by default.
Scopes — Next, check ✅ only the “
api” option in scopes. No other options are required.
How to Integrate BetterBugs Project with GitLab (for Self-Hosted Instances): Step-by-Step
PREREQUISITES for BetterBugs.io + GitLab Self-Hosted Integration
GitLab Application ID and Secret (as generated using the above steps)
Your GitLab Base URL (self-hosted)
Select GitLab Version for Integration: Self-hosted Version
You've two versions for it:
Cloud Version -> Enables you to connect BetterBugs with gitlab.com with OAuth.
Self-hosted -> Enables you to connect your self hosted GitLab project with your Personal Access Token.
Select the "Self-hosted" Version of GitLab.
Enter GitLab application credentials
Enter details for the GitLab application + your GitLab Base URL:
Client ID* — Application ID
Client Secret* — Secret
Base URL — GitLab Base URL
IMPORTANT
Make sure your GitLab Base URL (used during integration) does not end with a trailing slash.
For example: ✔️ https://gitlab.example.com
❌ https://gitlab.example.com/
Authorize BetterBugs.io for GitLab
Authorize BetterBugs.io for your GitLab account.
IMPORTANT NOTE
If you're on a free plan, Steps 6 and 7 are NOT REQUIRED. You can just SKIP to "How to Raise an Issue on GitLab using BetterBugs" section.
FOR PAID PLANS (Teams and Enterprise)
Steps 6 and 7 enables you to explicitly choose between:
Manual Issue Creation (Default): This means for sharing a bug report to GitLab, you'd need to manually populate fields for your GitLab Repo. (Project, Assignees, Labels, and others). Its a FREE FEATURE.
Automatic Issue Creation: This means for sharing a bug report to GitLab Repo, you can configure BetterBugs to auto-populate fields for GitLab (Project, Assignees, Labels, and others). Its a PAID FEATURE.
Optional: Choose your preferred method for creating tickets: Manually or Automatically
From the "Forward Bug Reports" dropdown, select your preferred method for creating tickets in your project tool:
Manually: Enables you to raise issues manually. Here, we've selected the manual method to showcase project integration steps.
Automatically: Enables you to raise issues with automation.
Okay! You're good to go with the Project level integration for GitLab Self-hosted version. Now, you can create detailed reports and share them as GitLab issues directly from your browser with a few clicks.
Last updated