45 ideas
What's the problem? 1. Search is difficult to use because it automatically filters out done/closed posts, when users may indeed be looking for a past issue. 2. Users can't see the filters actively applied to a search. 3. Users can't see the labels and filter the posts by them easily. 4. Users can't see the statuses and filter the posts by them easily. 5. Should be a default view for 'created by me' and 'followed by me' so the users can track what matters to them, not see everything. ### What's the solution? These problems are mostly solved already in the admin's view. The admin panel's functionality is much better than what the users get in the portal. I'm not sure why there's the need to create two different UIs. I would use the admin panel's UI in the user portal (obviously omitting features that are reserved for admins).
The theme settings are not reflected in the emails. The button is still yellow instead of gray in our case for example.
Canny allows to add a comment to a status change. We used this a lot for bigger communications where we either explain the status change, thank the user, or mention the release notes in the completion message. They then only get one email with the status change and the message.
Native SDKs for iOS and Android that let teams embed the Quackback feedback widget directly inside their mobile apps, just like the existing web widget. Problem There's no way to collect in-app feedback on mobile. Users have to leave the app to submit ideas, which adds friction and lowers engagement. Proposed Solution - Native SDKs (Swift/Kotlin) with the same core experience as the web widget: submit ideas, vote, and view status updates. - Customisable theming including dark mode to match the host app. - Automatic user identification so feedback is tied to the right account. - Floating button trigger or programmatic activation. Why It Matters Many products are mobile-first. Collecting feedback where users already are leads to better engagement and closes a key gap with commercial alternatives.
Using Settings > Notifications > Pause all email, didn't prevent status updates or new comments from being notified via email to users. The individual email toggle for each action was turned on, at first but then we turned it off, and it was still failing. Expectation was that with "Pause all email" toggled on, no one would get emails about anything, so this looks like a bug.
Search is such a central interaction that it feels wrong to hide it behind a button. I'd prefer it to be a primary interface.
I would love to have the option to have it send customer weekly (or defined) digest of new feedback (feature request and/or Bug Reports) to help keep them engaged.
I cannot find the option to reorder columns (statuses) in Roadmap view. It's quite frustrating to see "Closed" before "Complete".
The widget's actual light/dark rendering is controlled from the vendor's own workspace admin console, not the embedding page: Admin → Settings → Branding → Theme Mode, with three states — "User choice (allow toggle)", "Light only", "Dark only" (https://quackback.io/docs/admin/branding, "Theme Mode" section). This is a static, per-workspace setting stored server-side and rendered inside the widget's own iframe. Our SPA has no channel to pass its data-theme attribute into that iframe: the SDK command surface simply does not expose it. Widget theming should be controlled programmatically by the hosting application, not hard-coded by the admin page.
...or as featured media to display it in a player/viewer at the top of the post
🚀 The Problem Quackback brilliantly combines a Help Center, a Support Inbox, and Feedback Boards. However, forcing us to choose a single subdomain to host it (e.g., only help.domain.com or only feedback.domain.com) compromises the user experience: - Frustrated users looking for a support ticket on a feedback.yourdomain.com URL is confusing. - Users wanting to upvote the roadmap on a support. or help. subdomain is similarly unintuitive. 💡 The Solution Allow a single Quackback instance / workspace to map multiple subdomains to specific QB modules as entry points: - help.yourdomain.com ➔ Routes directly to the Knowledge Base / Help Center. - support.yourdomain.com ➔ Routes directly to the Ticket Submission Form. - feedback.yourdomain.com ➔ Routes directly to the public Feature Voting & Roadmap. 🌟 Why This Adds Value - Enterprise UX: Matches industry standards by sending users exactly where their intent dictates. - The Ultimate All-in-One: Completely replaces the need to run separate, fragmented tools (like Zendesk + Canny) just to get the right URLs.
It would be useful for a user writing feedback to have the option to select a tag. In our case, we use tags to categorize our features. If a user needs to submit improvement feedback on a feature, they know which feature it is, so they could potentially add the tag themselves.
Please add a feature that every feedback submission on a board is automatically assigned to a roadmap. e.g. add to every feedback board a "linked roadmap" that the feedback submission is automatically assigned to. I want to not waste time having to automatically assign every feedback in the bug reports board to the bug tracker roadmap/product roadmap.
Hi there, I would like to propose an integration for steam/steamworks to track reviews, feedback on the forum and comments on blog posts. This would offer a massive help with integrating steam for tracking important sentiment in GameDev. Quite sure it could also provide a massive new market with lots of indie games considering stuff like this rn.
In our current solution (Discourse based), we limit users to 20 votes each. They can retract their votes to "re-spend" them and when a request is implemented that vote still shows on the request, but they get it back into their pool of votes. In effect, they can only vote on 20 not-yet-complete features at any one time. This is very important to us as it forces our users to vote for their top 20. If they don't know what they top 20 requests are, how are we meant to!
Body: Voting permissions are configured per board today, but the roadmap is a display layer over posts that live on those boards — so there's no way to control voting on the roadmap independently. That blocks a common setup: users vote freely on new feedback and ideas, while the roadmap stays a read-only, informational view. Once something is planned, the prioritisation decision is already made; further votes there add noise and suggest the order is still negotiable when it isn't. Proposal: a per-roadmap toggle "Allow voting on roadmap items", default on so nothing changes for existing workspaces. When off, the vote button is hidden on the roadmap view; existing vote counts stay visible as read-only context. Optionally reuse the existing permission tiers (Anyone / Signed-in / Segments / Team only) instead of a plain toggle, for consistency with the board matrix.
Bulk edits for feedbacks on boards, e.g. set new status to all selected feedbacks.
By default, Quackback creates an issue in Linear when a new post is made. But what if someone already has an issue in Linear and wants to link it to a new Quackback post? I'm not sure if this is possible or if it would complicate the current setup. If possible, add a small section in the "Manage" area when viewing a post in the admin. It should display something like "Linear:" with a status of "Linked" or "Not Linked." If linked, show the issue code with a hyperlink; if not, allow it to be linked either through a link or by entering the issue code or number. You could even color-code it as well; red for unlinked, green for linked.
For posts that include images, it would be helpful if clicking an image opened it in a lightbox with a larger preview.
