No. SleekView Feedback reads the existing csc_event_status option rows and meta that Cron Status Checker 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 all analytics stay aligned across Cron Status Checker, SleekView reports, and any export.

Yes. The Feedback view inherits the same query filters as the SleekView Tables and Charts surfaces. You can restrict by status, category, language, or any custom meta. Most teams expose only New, Planned, and Shipped statuses on the public board and keep internal review or archived rows hidden behind the admin entirely.

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 audience already has accounts. Vote totals stay consistent across pageloads and devices for known users, with cookie based dedupe handling all anonymous voters cleanly.

A separate roadmap tool is a different product with its own database, login, and pricing. You sync rows across, then maintain two sources of truth. SleekView Feedback reads Cron Status Checker data live, so the public board, the agent queue, and the analytics dashboards always show the same numbers. There is nothing to sync because there is only one source.

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 or PHP to change which fields drive which pill.

By default upvotes update the meta silently to avoid notification spam in busy agent inboxes. You can opt in to firing a custom action on each upvote if you want agents to see live demand inside their existing notification flow, or threshold it to alerts every fifty or one hundred votes for a calmer daily summary rhythm rather than per click pings.

Yes. SleekView lets you scope the query to one or many terms in any taxonomy Cron Status Checker writes, so you can run a board per product line, per language, or per audience segment. Each board is a separate block on a separate page, all reading from the same underlying store with their own filter and field mapping values configured independently.

Because SleekView Feedback reads whatever query you point it at, you can swap the source from csc_event_status option to a different post type or table without rebuilding the board. The cards, badges, votes, and filters stay intact. You only re map the column roles in the block settings, and the public URL plus all existing vote counts stay the same throughout the transition.