Both work. SleekView reads whichever data source you nominate, so the feature set of BigCommerce Bridge for WordPress itself does not constrain what SleekView can show on the board. The free version plus a feedback CPT is already enough to run a useful board, and paid tiers simply give you more sources you can point at and more meta keys to map onto pills and tags.

Both setups work. SleekView reads any post type, custom table, or saved query you point it at, including data BigCommerce Bridge for WordPress itself writes. Most teams add a feedback CPT for new requests and keep BigCommerce Bridge for WordPress tables as a separate filterable source they can also surface as cards on the same board.

You add a numeric column or a postmeta key during setup, and SleekView increments it on every vote. The simplest path is a single integer field on the feedback row; advanced setups use a separate votes table so you can audit duplicates and identify the voter and run later moderation reports.

Yes. SleekView Feedback respects WordPress roles and capabilities. Require login, restrict voting to a custom role like reviewer, or open the board to anonymous visitors with cookie and IP rate limiting. Internal triage boards usually require login; public roadmaps usually allow anonymous votes from any visitor.

Yes. Map the status pill to the column that already drives your workflow. Closing the request in admin updates the pill on the next page load, and flipping the pill on the board writes the new value back to that column, so the board and source list always agree.

Yes. SleekView Feedback accepts a saved query as the source, so you can show only requests touching a specific tag, only Investigating ones, only ones tagged for a client, or any combination. Each board you embed can use a different filter without forking the source rows or duplicating data.

By default it is only a SleekView signal. BigCommerce Bridge for WordPress keeps doing what it does; SleekView writes votes back to your feedback source row. If you want votes to influence anything else, hook the SleekView vote action and update whatever target you want, like a priority field or a webhook or a chat ping.

GitHub and Linear sit outside WordPress, so a request loses the link to the actual data row or product it refers to. SleekView Feedback runs on top of your own database, which means a vote, a status change, or a flag stays attached to the row, survives staging clones, and travels with database migrations cleanly.