Multi-Subdomain Routing for core QB Features (help / support / feedback)

🚀 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.

Allow disabling votes per roadmap (separate from board voting permissions)

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.

iOS and Android widget

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.

Reorder columns in Roadmaps

I cannot find the option to reorder columns (statuses) in Roadmap view. It's quite frustrating to see "Closed" before "Complete".

E-Mail Digest

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.

Vote budgets

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!

Adding the ability to upload inline video with size limitation

...or as featured media to display it in a player/viewer at the top of the post

Default Roadmap per Board

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.

User can add tag on feedback ?

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.

Widget ignores new-post board targeting

The documented open({ view: "new-post", board }) command opens the widget but does not navigate to the submission form or select the requested board.

Widget does not refresh boards after identify

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:

Allow editing changelog item date

Bulk edits

Bulk edits for feedbacks on boards, e.g. set new status to all selected feedbacks.

More granular OIDC Provider config

I opened an exploratory PR for widening the compatibility with non-standard OIDC providers, my specific use case is the EVE Online SSO Provider. Key issues with this provider, which the PR extends Quackback to support in a generic fashion (config options over a specific integration): - Advertises OIDC discovery but returns no id_token at all - Its userinfo endpoint (/v2/oauth/verify) returns PascalCase fields (CharacterID, CharacterName, …) with no sub/id - Never releases an email — EVE identities don't have one - The actual identity lives in the JWT access token: sub: "CHARACTER:EVE:", name: "" https://github.com/QuackbackIO/quackback/pull/337

Allow for Complete and Closed groupings to be re-ordered just like the items inside them

Currently you can only drag and drop the items within each group on the Statuses screen. This means that Closed always appears before Complete for me and that's annoying as I want it to be last. I can't drag and drop it like I can with individual items inside. It's quite misleading too since the Complete appears before it on the Admin page but then in the Roadmap screen it's after.

Add the ability to manually link posts to already created Linear issues

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.

Extend Linear sync

Support syncing of: - Images - Comments - Labels - ...

Adding Direct chat

why not supporting instant screen shot for bug

do this support a screenshot

Lightbox

For posts that include images, it would be helpful if clicking an image opened it in a lightbox with a larger preview.