KanbanWP stores tasks, statuses, boards, and estimates in its own custom tables rather than postmeta. The board UI is fast for moving cards, and that same architecture means the WordPress Posts screen never sees the data. Asking which assignee carries the most work, which board is over WIP limit, or which tasks have been sitting in In Progress for two weeks takes a column-by-column count on the board itself.

SleekView reads the KanbanWP custom tables directly through its schema-discovery UI. The kanban_task table joins to kanban_status for status names, to kanban_board for board names, and to kanban_estimate for hour estimates. Title, status, board, assignee, estimate hours, and modified date sit as proper columns you can sort, filter, and group across every board at once.

The board keeps owning the drag-and-drop experience. The table view becomes the cross-board audit surface, so a team lead can answer questions about workload, age, and throughput in one filtered query instead of a tour across columns.

KanbanWP chose to store tasks in custom tables instead of postmeta, which is the right call for board performance and the reason its data hides from every standard WordPress list. A team lead asking how much work each engineer is carrying, which board is over its WIP limit, or which cards have not moved in two weeks gets no answer from the board view and no answer from the Posts screen. SleekView's schema-discovery UI sidesteps the usual custom-table problem (you do not need to know table names ahead of time) and exposes kanban_task, kanban_status, kanban_board, and kanban_estimate as joinable columns.

The board keeps owning drag-and-drop, while leads get the cross-board audit grid that delivery work actually requires.