No. SleekView Feedback reads the moodle_course post type and forum thread mirror that Moodle Bridge WP already writes when it syncs from the Moodle Web Services API. There is no separate roadmap table, no extra sync job, and nothing to migrate. Upvotes are stored as numeric meta on the same row your bridge reports chart against.

Yes. The Feedback view inherits the same query filters as SleekView Tables and Charts. You can restrict by course status, Moodle category, faculty, review state, or any custom meta. Most Moodle teams expose only courses tagged Roadmap or Bug with statuses Planned, In progress, and Shipped on the public board and keep the rest hidden.

SleekView tracks upvotes per browser through a signed cookie and per user ID for logged-in WordPress users. You can also require a Moodle SSO login before voting if you want stricter dedupe. Vote totals stay consistent across page loads and devices for known users, with cookie-based dedupe protecting anonymous voters from double counting their own upvote.

A separate roadmap tool is a different product with its own database, login, and pricing. You sync Moodle courses across twice, then maintain two sources of truth. SleekView Feedback reads the Moodle Bridge mirror live through WordPress, so the board, the bridge, and Moodle itself always settle to the same numbers. There is one source of truth: your WordPress install.

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 Moodle Bridge 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 Moodle admins. You can opt in to firing a standard WordPress action on each upvote that you bridge into Moodle webhooks 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 mirrored from Moodle, so you can run a board per faculty, per instructor, or per language. Each board is a separate block on a separate page, all reading from the same underlying mirror with their own filter and column mapping configured.

Because SleekView Feedback reads whatever query you point it at, you can swap the source from moodle_course 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 visitors and search engines alike.