Issue Tracking

Quackback + GitLab

Connect feedback to GitLab Issues

Teams that self-host their DevOps pipeline on GitLab need feedback to flow into the same platform where merge requests and CI pipelines run. The Quackback GitLab integration creates issues from feedback posts in any GitLab project, including self-managed instances. Issues carry the post description, vote count, and mapped labels. When a merge request closes the linked issue, the feedback post transitions to "Shipped" and voters are notified. Development teams working entirely within GitLab get user-demand context alongside their code, without adopting another SaaS tool for feedback management.

How it works

Connect GitLab to Quackback in three steps.

Connect your GitLab instance

Enter your GitLab instance URL and authorize access with an API token. Works with GitLab.com and self-managed deployments.

Select projects and labels

Choose which GitLab projects receive issues from each Quackback board, and map tags to GitLab labels.

Issues link to merge requests

Created issues include feedback context and backlinks. Closing an issue via merge request updates the feedback post and notifies voters.

Why connect Quackback to GitLab

Works with self-managed GitLab

Point the integration at any GitLab instance URL, including on-premise deployments. Teams with strict data residency requirements can keep feedback linked to their infrastructure without routing data through a third party.

Feedback travels with merge requests

Issues created from feedback include a backlink to the original post. When a developer opens a merge request that references the issue, reviewers see exactly which users requested the change and how many votes it received.

Milestones reflect user priorities

Assign feedback-driven issues to GitLab milestones during creation. Release planning meetings can filter the milestone by vote count to see which user-requested features are included in the upcoming release.