If your team plans and ships in GitLab, user feedback belongs next to the rest of your issues. When someone hits a bug on your site, it should arrive as an issue your developers can triage, not as an email that gets lost.
How it works: add the Saber Feedback button to your website or web app, connect it to a GitLab project, and every feedback report becomes a new GitLab issue. Each issue includes the user’s message, their screenshot, the page they were on, and their browser and device details. Your users don’t need a GitLab account.
- Set up the GitLab integration in three steps
- What each GitLab issue includes
- Saber Feedback vs GitLab Service Desk
- Ask for the feedback your team needs
- Frequently asked questions
Set up the GitLab integration in three steps
1. Add the feedback button to your site
Sign up for a 30-day free trial, create a feedback form, and paste the code snippet into your website. It takes a few minutes, and there are plugins and guides for WordPress, Shopify and other platforms. Our guide on how to add a feedback button to your website walks through it.
2. Connect your GitLab account
In the Saber Feedback app, open Third-party Integrations, click Setup New Integration and choose GitLab. If you run your own GitLab server, enter its address first; otherwise leave it set to GitLab.com. Click Connect and authorize Saber Feedback. There’s no token to copy: Saber Feedback connects to GitLab with OAuth.
Then choose the project for new issues and set the issue title. You can include a summary of the user’s message in the title automatically, and add labels such as user-feedback so these issues are easy to find on your issue boards.

3. Send a test report
Click Test Settings to send a sample report to GitLab and check the issue arrives as expected, then save. From then on, every feedback report from your site creates a new issue in that project.
The GitLab integration help doc has every setting in detail.
What each GitLab issue includes
Saber Feedback collects the information a developer needs to reproduce a problem, so nobody has to go back to the user to ask which page, which browser, or what they saw. Each issue is written in Markdown and can include:
- The user’s message
- Any screenshot they attached
- Any category or rating they chose, if your form includes them
- The page URL
- The user’s browser, browser plugins, operating system and screen size
- The user’s email address, if they gave it or you passed it in from your app
- When the feedback was submitted
- A link back to the full report in your Saber Feedback account

Once the issue is in GitLab, you handle it like any other: assign it, move it across your issue board, add it to a milestone, and close it from the merge request that fixes it.
Saber Feedback vs GitLab Service Desk
GitLab’s Service Desk turns emails into issues, which works well for support requests. But an email from a user rarely says which page they were on or which browser they used, and it never includes a screenshot unless they think to attach one. Saber Feedback collects the report on the page where the problem happened.
| GitLab Service Desk | Saber Feedback | |
|---|---|---|
| Where users give feedback | By email | On any page of your site, from a feedback button |
| Screenshot of the page | Only if users attach one | Yes, taken from the feedback form |
| Page URL, browser and device details | Only if users type them | Added automatically |
| Structured questions, such as a category or rating | No | Yes, 14 field types |
| Price | Included with GitLab | From $99/month, on plans with screenshots and integrations |
Ask for the feedback your team needs
Forms can be as simple or detailed as you like. Choose from 14 field types, including text boxes, dropdowns, checkboxes, and star and emoji ratings, and show follow-up questions based on earlier answers. You can use different forms on different parts of your site: a bug report form in your app, and a content feedback form on your marketing pages.

You can style the feedback button to match your site, or open the form from your own link or icon.
Frequently asked questions
Do my users need a GitLab account?
No. Users fill in the Saber Feedback form on your site, and Saber Feedback creates the issue using the GitLab account you connect. Your users never see GitLab.
Does it work with self-managed GitLab?
Yes. Enter your GitLab server’s address when you set up the integration. Your server must be reachable from the internet so Saber Feedback can create issues.
Can I send feedback to more than one GitLab project?
Yes. Each feedback form has its own integrations, so bug reports from your app can go to its project, and feedback from your marketing site to another.
Can feedback go to other tools as well?
Yes. Saber Feedback also integrates with Jira, Linear, GitHub, Asana, Trello, Basecamp, Redmine and Slack, and can send feedback by email or webhook. See all integrations.
Where can I use the feedback button?
On almost any website or web app, including staging and test sites, client sites during a redesign, customer portals, WordPress and Shopify sites, and most learning management systems.
Try Saber Feedback with GitLab free for 30 days
Set up a feedback button that sends complete, actionable reports straight to GitLab. No credit card required.