Feedbucket and Gitlab integration
Feedbucket can deeply integrate with Gitlab. That means that your team should be able to manage all feedback inside of Gitlab instead of in the Feedbucket Admin.
Install the Gitlab integration on your Feedbucket project
- Go to your project and then click the tab
Integrations. - On the integrations page click the button
Connectnext to Gitlab as show in the image below.

- If this is the first time you are connecting Feedbucket and Gitlab you will be redirected to Gitlab where you have to allow Feedbucket. Once the connection between Feedbucket and Gitlab has been established you will be redirected back to Feedbucket.

- You will now see a green bar on the Gitlab integration that indicates that the connection is made. The settings should have opened automatically but in case it doesn't, click on the
Settingsbutton to start configuring the Gitlab connection for this project.
Configure the Gitlab integration to your needs
Most often, you will create one Feedbucket project per client website you are building. That way you can connect each project to a specific project in of Gitlab as well. It's up to you how you want to configure it.
After you connect you should see the configuration pop-up. If you don't, just click on the Open Settings button.
- Select the project. You should see all projects that the account you connected with is an owner of. If you do not see your project in this list make sure to check the permissions in Gitlab.
- Optionally, you can select labels that you want the issues to have when created from Feedbucket.

How to use the Gitlab integration
Once you have configured everything as you wish, below is how the integration should behave.
When new feedback is created
Whenever a new piece of feedback is created in Feedbucket, a issue will be created in Gitlab. This issue will be placed in the project that you selected in step #1 above. If you set any labels as in step #2, the issue will automatically have these labels. The issue will automatically have all of the technical details that Feedbucket collected like the session information of the reporter, the screenshot/recording etc.
When a new comment is created on feedback
A piece of feedback can have lots of comments as a thread to communicate and collaborate. When a new comment is created on a piece of feedback that has been created in Gitlab by Feedbucket, that comment will also be created in Gitlab under the correct issue. That way, all comments that happens in Feedbucket will automatically be pushed to Gitlab as well.

As you can see in the image the real power lies in the two-way communication here. If your team needs to ask a follow-up question that can be done without leaving Gitlab. All you have to do is to add a new comment that starts with @feedbucket and it will automatically be pushed over to Feedbucket and notify the client of this new comment from you. Regular comments submitted without the prefix of feedbucket will not sync over so you can continue to keep your internal conversations flowing in Gitlab.
When the feedback is resolved
If the feedback gets resolved from Feedbucket, the issue will automatically be closed in Gitlab.
Again, there is a 2-way integration here as well. If your team has completed the feedback they can close the issue inside of Gitlab and it will automatically resolve in Feedbucket. This way your team can manage all aspects of the feedback without leaving Gitlab.
When the feedback gets re-opened
If the feedback gets re-opened from Feedbucket we will open the issue in Gitlab again.
We have 2-way integration here as well. If you re-open the issue inside Gitlab it will be re-opened in Feedbucket as well.
FAQ
What permissions are required to integrate with Gitlab?
You should be an owner of the project that you try to connect with.
How to disconnect the Gitlab integration
When the Gitlab integration is active you will see a button for Disconnect. Click this to disconnect your Gitlab integration with this project.

Updated on: 12/02/2026
Thank you!
