17 ideas
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.
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.
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.
At the moment in the Admin Area posts can be sorted by "Newest", "Oldest" and "Top Votes". Adding "Manual" sorting where Admins can drag and drop posts to sort them for the team for further processing would be helpful. This doesn't need to be visible to public users, but would be practical to pre-sort for product managers.
The documented open({ view: "new-post", board }) command opens the widget but does not navigate to the submission form or select the requested board.
Short summary: With Signed-in boards, verified widget identification succeeds and authenticated capabilities return canSubmit: true, but the widget keeps the anonymous board list. No board is selected, so Submit remains disabled. Detailed Markdown:
It would be interesting to add an option for users to leave feedback on changelog posts. Options: 1. 5 stars, where users can rate the update from 1 to 5 stars. 2. Upvote and downvote. This feedback is important so we can gather users' opinions about the updates.
It would be useful to have the option to define which board should be preselected when the page loads.
Now we can select Spaces, and Folderless List, but we need to link List inside a Folder
The roadmap screen starts hiding the 4th column on a standard 1920x1080 monitor which means even with just "Open, Planned, In Progress and Complete" the Complete column is half cut off as Quackback won't take up the full width of the page. This is even more annoying if you have a Closed column too as most users will never scroll to the right to see it.
It would be most beneficial if existing users and admins could link an external account from a supported sign-in provider to their account regardless of their email. Users and especially admin may not have the same email across the supported and enabled sign-in providers, designated company SSO for admin sign-in which leads to admins and users creating duplicate accounts when selecting from the list of available sign-in providers.
It would be great if the tags were to be sortable (or at least sorted). Both in the admin portal /admin/settings/tags and when creating a post. When adding new tags retroactively they get out of order with other tags of the same category. Nested tags with category: tag would also be amazing, but it potentially is an unnecessary complication.
Hi Team.Loving Quackback at the moment and setting it up for our PatchMon project.One thing i've noticed is that when trying to sync github issue statuses by enabling the toggle in the integration settings, i'm getting the following: Failed to register webhook: GitHub API error 404: {"message":"Not Found","documentation_url":"https://docs.github.com/rest/repos/repos#update-a-repository","status":"404"} I am on version 0.13.1 (:latest)I have found (through a bit of Claude Code) that it could be due to the error in file : apps/web/src/components/admin/settings/integrations/github/github-config.tsx on Line 161 where it needs to be value={repo.fullName} as opposed to value={repo.id.toString()}> We also needed to handle the param for clarity on lines 89-91 on the same file.I have amended and rebuilt the container in my production container and found that it will now work by pulling the statuses and mapping them correctly.t
