Dark mode is here. Turn it on in Settings > Appearance, or let your system preference decide. Text and controls also have stronger contrast, so everything is easier to read.
Use cases / Bug tracking
Bug tracking for the bugs customers find
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.
Start collecting bug reports
- 14-day Pro trial, no card needed
- Choose Free or a paid plan when it ends
- Open source. Self-host with Docker
The widget your customers see inside your app.
Example data. What follows is an interactive demo of a made-up workspace called Acme. Its customers, posts, votes and changelog entries are examples, not Quackback's own.
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.
Who it's for
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.
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 boardsExample data. What follows is an interactive demo of a made-up workspace called Acme. Its customers, posts, votes and changelog entries are examples, not Quackback's own.
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 inboxExample data. What follows is an interactive demo of a made-up workspace called Acme. Its customers, posts, votes and changelog entries are examples, not Quackback's own.
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 pageExample data. What follows is an interactive demo of a made-up workspace called Acme. Its customers, posts, votes and changelog entries are examples, not Quackback's own.
Acme Corp status
- Scheduled We're upgrading our primary database. The app may be read-only for up to 10 minutes.
Core platform
Notifications
Integrations
Past incidents
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 changelogExample data. What follows is an interactive demo of a made-up workspace called Acme. Its customers, posts, votes and changelog entries are examples, not Quackback's own.
Drafts now save on the device and sync the moment you are back online.
Connect your workspace to Slack to hear about new feedback, votes and status changes as they happen. Send each board to its own channel so the right team sees it.
Save your layout, logo and payment terms once and reuse them on every invoice.
What customer bug tracking needs
One report per bug
Who's affected
Two-way issue sync
Screenshots and context
Reporters kept in the loop
A status page included
Common 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.
Have another question? Talk to the team.