No. SleekView Feedback reads the nt_wmc_folder custom table and folder meta that FileBird Pro already writes. There is no separate roadmap table, no sync job, and nothing to migrate. Upvotes are stored as numeric meta on the same row your FileBird reports chart against, so totals stay aligned across the staff board and the admin.

Yes. The Feedback view inherits the same query filters as SleekView Tables and Charts. You can restrict by folder status, parent folder, mime rule, review state, or any custom meta. Most FileBird teams expose only folders tagged Roadmap or Bug with statuses Planned, In progress, and Shipped on the staff board.

SleekView tracks upvotes per browser through a signed cookie and per user ID for logged-in WordPress users. Staff boards require a WordPress account by default, so dedupe is enforced per user id without extra setup. Vote totals stay consistent across page loads and devices for known editors on the FileBird board.

A separate roadmap tool is a different product with its own database, login, and pricing. You sync folders across, then maintain two sources of truth. SleekView Feedback reads FileBird data live through WordPress, so the board, the folder tree, and the FileBird admin always show the same numbers. There is one source of truth.

Yes. Any numeric meta key can act as the vote column, any taxonomy or text meta can be the status, and any taxonomy or meta can be the category. The SleekView block exposes a dropdown for each role so you map the FileBird columns once through the block UI and never touch the underlying template to change which fields render.

By default upvotes update the meta silently to avoid spamming busy editors. You can opt in to firing a standard WordPress action on each upvote that you bridge into Slack or email if you want owners to see live demand, or threshold it to alerts every ten or fifty votes for a calmer notification cadence.

Yes. SleekView lets you scope the query to one or many terms in any taxonomy, so you can run a board per parent folder, per smart rule, or per editor. Each board is a separate block on a separate page, all reading from the same underlying FileBird store with their own filter and column mapping configured.

Because SleekView Feedback reads whatever query you point it at, you can swap the source from nt_wmc_folder to a different post type or table without rebuilding the board. The cards, badges, votes, and filters stay intact. You re-map the column roles in the block settings, and the URL stays the same for editors and search engines alike.