# Bug tracking for the bugs customers find

> Bug tracking software for customer-reported bugs. Collect reports in one place, merge duplicates, sync to Linear, Jira or GitHub, and tell reporters it's fixed.

Source: https://quackback.io/use-cases/bug-tracking

Quackback is the front door for customer-reported bugs. Reports from your widget, portal and support inbox land on one board, duplicates merge, the fix goes to your issue tracker, and every reporter hears when it's resolved.

## Keep your tracker for engineers. Give customers a front door.

Jira, Linear and GitHub are built for the people fixing bugs. Customers need something else: a place to report a problem, see that it's known, and hear when it's fixed. Quackback sits in front of your tracker, counts who's affected and keeps them updated, while engineering keeps working where it already does.

- **Support teams**: Link a chat about a bug to its report, so the customer hears when it's fixed.
- **Engineering**: Get one issue with the reporter count and context, not twenty tickets.
- **Product teams**: See which bugs affect the most customers, and which accounts they are.

## From report to fix, in the open

A bug report follows the same loop as a feature request, with your issue tracker in the middle.

### 1. Customers report it once

A Bug Reports board on your portal and widget lets customers report a problem and see if someone already has. Matching reports appear as they type, so they add a vote instead of a duplicate.

[Explore feedback boards](https://quackback.io/features/feedback)

### 2. Support links what it hears

When a customer reports a bug in chat or email, add it to the report from the inbox. Their vote counts, and their words stay on the post as an internal note for whoever fixes it.

[Explore the inbox](https://quackback.io/features/inbox)

### 3. Post outages on your status page

When a bug takes something down, post an incident on your status page. Subscribers hear about it, and the AI agent can tell customers in chat what's going on.

[Explore the status page](https://quackback.io/features/status)

### 4. Tell everyone it's fixed

When the linked issue closes, Quackback moves the report along, or asks you to confirm first, depending on the tracker. Link a changelog entry to the fix and everyone who reported or voted gets the news.

[Explore the changelog](https://quackback.io/features/changelog)

## What customer bug tracking needs

- **One report per bug**: Merge reports of the same bug and every vote and comment carries across. Quackback AI suggests the merges for you.
- **Who's affected**: Every report lists the customers behind it, so you can see whether a bug hits ten free users or your biggest account.
- **Two-way issue sync**: New reports can open issues in Linear, Jira, GitHub and other trackers, and issue changes flow back as status updates. On Business.
- **Screenshots and context**: Customers can add screenshots and videos to a report, and the widget can attach session details you choose, such as app version.
- **Reporters kept in the loop**: Everyone who reported or voted is subscribed, and hears when the status changes or the fix ships.
- **A status page included**: Incidents, maintenance and uptime history in public, in the same workspace as your bug reports.

## Frequently asked questions

### How do you handle bug reports from customers?

Give customers one place to report bugs, such as a Bug Reports board on your portal and in-app widget. Merge duplicates so each bug has one report with an accurate count, link support conversations to it, and send confirmed bugs to your issue tracker. When the fix ships, notify everyone who reported it.

### Can I sync bug reports to Jira, Linear or GitHub?

Yes. On Business and above, connect Linear, Jira, GitHub, GitLab or another tracker and new reports can open issues there. When an issue moves, the change comes back to Quackback: Linear and GitHub update the report's status on their own; Jira, GitLab and most others suggest the change for you to approve. Voters hear when it's fixed.

### Does Quackback replace Jira or Linear?

No. Quackback is where customers report bugs and follow the fix. Your engineers keep planning and fixing in Jira, Linear or GitHub, and the integration keeps the two in step.

### Can customers attach screenshots to a bug report?

Yes. With rich media switched on, customers can add images and videos to a post from your portal or widget. If you identify users in the widget, each report is tied to their account, and you can attach session details such as their plan or app version.

### Is Quackback's bug tracking free?

The Free plan includes one board with up to 50 posts, so you can start with a bug board. Pro adds unlimited boards and posts, and Business adds issue tracker integrations. Every paid plan has a 14-day trial, and the open-source edition is free to self-host.

## Related

- [In-app feedback](https://quackback.io/use-cases/in-app-feedback): Let customers report bugs from inside your app.
- [Feature requests](https://quackback.io/use-cases/feature-requests): Track requests next to bugs, on their own board.
- [Linear integration](https://quackback.io/integrations/linear): Create issues and sync statuses with Linear.

Start a free trial: https://app.quackback.io/signup?plan=pro&from=markdown
