✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView Charts for Kanban for WordPress

Kanban for WordPress stores tasks, boards, and status changes in dedicated kanban_* tables. SleekView Charts rolls those rows into status donuts, time-in-status bars, and throughput trends the board UI cannot show.

♾️ Lifetime License available

SleekView Charts dashboard for Kanban for WordPress

Boards show flow, charts show stagnation

Kanban for WordPress writes to its own kanban_tasks, kanban_boards, and kanban_status_changes tables, keeping clean schema separation from the WordPress posts table. The plugin's board UI is excellent at visual flow and terrible at showing aggregate signals like 'how long do cards typically sit in review' or 'what is our throughput this month'.

SleekView Charts reads the same tables and turns them into a flow dashboard. Total open tasks, status distribution as a donut, average time-in-status per column as a bar, and throughput (cards completed per week) as an area chart make stagnation and velocity visible in seconds. The time-in-status metric joins kanban_status_changes for the latest transition timestamp, computing duration at query time.

Charts share the same data layer as the SleekView task table, so a filter on the table (board equals Q2 sprint, in-progress for over 5 days) reshapes every chart on the dashboard. The board UI keeps working for visual flow; the charts add the reporting layer that flow visualisations alone cannot deliver.

Workflow

From kanban_* tables to a flow dashboard

1

Connect kanban_ tables

Point SleekView Charts at kanban_tasks, kanban_boards, and kanban_status_changes. The plugin's status, board_id, assignee, and estimate columns are detected automatically.
2

Compute time-in-status

Join the latest row from kanban_status_changes per task and compute days since the transition. The metric becomes a chartable dimension for average time-in-status per column.
3

Pick flow KPIs

Total open tasks as a Number, status distribution as a donut, average time-in-status as a bar. Three cards already replace the per-board scan engineering leads do today.
4

Trend throughput

An area chart of cards completed per week shows velocity. Pin the dashboard at the sprint level so retros open with a real throughput number.

Sample dashboard

Charts you can build from Kanban for WordPress data

A flow dashboard built directly on kanban_tasks and kanban_status_changes, with status, board, assignee, and time-in-status as chartable dimensions.
Number · Default

Open cards across all boards

Top-line count of every task not yet done. The number engineering leads check before every standup.
Count
Pie · Donut

Cards by status

Distribution across to-do, in-progress, review, blocked, and done. The shape tells you whether the team is flowing or stuck on review.
Count group by status
Bar · Horizontal

Average time-in-status

Mean days per status column, computed from kanban_status_changes. Long bars on review or blocked columns flag bottlenecks.
Average(days_in_status) group by status
Area · Gradient

Cards completed per week

Throughput trend over time. Retros open with a real velocity number; sprint planning calibrates against the observed average.
Count group by completed_at

Comparison

Default Kanban board vs SleekView Charts

Default Kanban board

  • Board UI alone, no aggregate dashboards
  • Time-in-status is not visualised anywhere
  • Throughput trends require manual counting
  • Workload balance across users is invisible
  • Bottleneck columns surface only by eyeballing the board

SleekView Charts

  • Open-cards count as a Number KPI
  • Status donut for at-a-glance flow health
  • Time-in-status bar that ranks bottlenecks
  • Throughput area chart of cards per week
  • Workload bar by assignee across every board

Features

What SleekView Charts gives you for Kanban for WordPress

Bottleneck detection

A bar of average time-in-status per column ranks where cards actually sit. The review column with a 6-day average is the bottleneck; the dashboard says so without a manual scan.

Workload balance

A horizontal bar of open cards per assignee across every board. Capacity imbalances surface before standup, not after a missed sprint.

Real throughput

An area chart of cards completed per week turns velocity into a number. Sprint planning calibrates against observed throughput instead of optimistic estimates.

Audience

Who builds Kanban charts dashboards with SleekView

Engineering leads

A daily flow dashboard with status donut, time-in-status bar, and throughput area chart. Standups open with three numbers instead of a board scan.

Operations

Workload bars per assignee and throughput trends per board. Capacity planning becomes a saved dashboard, not a weekly spreadsheet.

Retros and planning

Throughput area chart and bottleneck bar as the opening slides of every retro. Velocity gets a real number; bottlenecks get a name.

The bigger picture

Boards are flow tools, charts are stagnation tools

Kanban boards are exceptional at showing flow and terrible at showing stagnation. A card that nobody touches for two weeks looks identical to a card that moved through three columns yesterday; both sit in a lane and wait. The plugin's design choice to store status changes in a dedicated kanban_status_changes table makes the data available, but the board UI does not surface it because boards are visual flow tools, not stuck-work dashboards.

Aggregate charts close that gap. A donut of cards-by-status shows the flow shape in a glance. A bar of average time-in-status per column ranks bottlenecks: a 6-day average on review is a different problem than a 6-day average on blocked, and the dashboard says which.

A throughput area chart turns velocity from a vibes word into a number engineering leads can plan against. SleekView Charts reads the same kanban_* tables the plugin writes to, computes time-in-status at query time from the latest status_changes row, and renders the dashboard inside the same admin where the board lives. The board keeps owning flow; the charts own the operational signals boards cannot show.

Questions

Common questions about SleekView Charts for Kanban for WordPress

SleekView Charts reads kanban_status_changes for each task's latest transition timestamp and computes days since that transition at query time. No cron job, no denormalised cache, the value stays fresh because it is computed live against the same table the plugin writes to.

 

Yes. kanban_boards joins to kanban_tasks via board_id. A donut of cards-by-status per board or a bar of throughput per board surfaces board-level differences, useful when one team runs multiple sub-boards like frontend, backend, and design.

 

Yes. kanban_estimates stores per-task estimates. Pair with status-change timestamps to compute actual duration from in-progress to done, then chart the variance. A bar of average overrun per task type becomes a calibration signal for future planning.

 

Yes. Charts are read-only against the kanban_* tables. The board UI continues to render, the drag-and-drop transitions still write to kanban_status_changes, and SleekView Charts picks up the new transitions on the next refresh.

 

Yes. Charts and Tables share the same data layer. A filter applied on the SleekView task table (board equals Q2 sprint, status equals in-progress) reshapes every chart on the matching dashboard, so drill-down stays consistent.

 

Yes. Aggregations run against indexed columns on kanban_tasks. Cache-duration controls keep repeated refreshes cheap. The time-in-status computation uses a subquery against kanban_status_changes that stays cheap because the plugin indexes status_changes by task.

 

Yes. Each card exports as PNG and as CSV. Throughput trends per sprint and bottleneck rankings per board are exactly the kind of artefacts retros and quarterly reviews ask for, ready in one click.

 

Yes. Per-task meta columns the plugin exposes become chartable dimensions. A custom priority column or a billing flag can be turned into a donut or a bar with no custom SQL, as long as the field is stored on the row.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

EUR

once

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView