No. SleekView Feedback reads the existing visionhd_ticket posts, post meta, and taxonomies that your Vision Helpdesk bridge 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 agents see in the admin, so reports stay aligned across the board.

Yes. The Feedback view inherits the same query filters as the SleekView Tables and Charts surfaces. You can restrict by ticket status, department, priority, asset, or any custom meta key. Most Vision Helpdesk teams expose only Planned, In progress, and Shipped statuses on the public board and keep open or internal tickets behind the staff portal.

SleekView tracks upvotes per browser through a signed cookie and per user ID for logged-in users. You can also require a WordPress account before voting if your customer base already has accounts through the customer portal. Vote totals stay consistent across pageloads for known users, with cookie-based dedupe for anonymous voters.

A separate roadmap tool is a different product with its own database, login, and pricing. You sync tickets across, then maintain two sources of truth that drift apart over time. SleekView Feedback reads Vision Helpdesk data live, so the board, the queue, and the reports always show the same numbers. One source of truth, in WordPress.

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 columns once through the block UI and never touch the underlying template to change configuration in the future.

By default upvotes update the meta silently to avoid notification spam in busy agent inboxes. You can opt in to firing the standard Vision Helpdesk ticket updated action on each upvote if you want agents to see live demand inside their existing workflow, or threshold it to alerts every ten or fifty votes for a calmer cadence instead.

Yes. SleekView lets you scope the query to one or many terms in any Vision Helpdesk taxonomy, so you can run a board per product line, per language, or per service tier. Each board is a separate block on a separate page, all reading from the same underlying ticket store with their own filter and field mapping values configured cleanly.

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