SleekView Kanban for Teamwork for WordPress
Teamwork for WordPress mirrors projects, task lists, and tasks into custom tables. SleekView Kanban reads those tables and groups tasks by status or task list, with assignee, priority, and due date on every draggable card.
♾️ Lifetime License available
Teamwork tasks rendered as a board inside WordPress
Teamwork for WordPress mirrors your installation into a set of custom tables. Tasks live in teamwork_tasks with id, name, description, tasklist_id, status, priority, assignee_id, due_date, and completed on every row. Task lists sit in teamwork_tasklists, projects in teamwork_projects, users in teamwork_users. The plugin admin shows a paged list sorted by sync timestamp.
SleekView Kanban reads those same tables and groups teamwork_tasks by status so the columns map to Teamwork's New, Reopened, Started, and Completed states. If you prefer Teamwork's list view, group by tasklist_id instead and each task list becomes a column. Card fronts show name, assignee name from teamwork_users, priority as a colored pill, and due_date with overdue highlighting.
Dragging a card from New to Started writes the new status to teamwork_tasks and queues the change for the next Teamwork API push. Cards with priority set to high render an amber pill so the urgent rows stand out without filtering. Tasks where deleted is true are filtered out by default so the board reflects active work only.
Workflow
From teamwork_tasks to a status board in four steps
Point SleekView at the Teamwork tables
Pick the column that becomes columns
Choose what shows on each card
Enable drag and write-back
Sample board
Sample Teamwork for WordPress tasks board
Comparison
Default Teamwork for WordPress vs SleekView Kanban
Default Teamwork for WordPress
- Synced tasks land in a flat admin table sorted by sync time, not by status
- No drag-and-drop in WordPress, status changes only happen in Teamwork itself
- Priority is hidden under a column toggle instead of being visible per card
- Cards do not combine assignee, due date, and priority on a single line
- Embedding a project board on a frontend page is not part of the plugin
SleekView Kanban
-
Group cards by
statusfor a New, Reopened, Started, Completed board -
Or group by
tasklist_idto mirror project task lists exactly -
Card fronts show
name, assignee,prioritypill,due_date -
Overdue rows turn rose using a
due_datevs today comparison -
Drag-and-drop writes
statusback, queued for the next Teamwork push
Features
What SleekView Kanban gives you for Teamwork for WordPress
Priority pills on every card
SleekView reads priority from teamwork_tasks and renders a colored pill on the card front, low to blue, medium to amber, high to rose. Filter the board by priority and only urgent rows render across all status columns at once.
Assignees joined and visible
assignee_id joins to teamwork_users so cards display real names and avatars. Filter by one assignee to scope the board to a single person, useful for daily standups or for weekly one-on-one planning sessions in WordPress.
Drag writes back to Teamwork
Moving a card from New to Started writes the new status to teamwork_tasks and queues the change for the next sync. The card stays in its new column locally so the team is not blocked while the API round-trip completes.
Audience
Where a Teamwork board inside WordPress fits the workflow
Client project portals
Filter to one project and embed the board on a private client page so they see active work without a Teamwork seat.
Daily team standup
Group by status, filter to active assignees, and run standup off a single board URL with no extra prep deck or report.
Sprint cleanup
Open the board grouped by status and drag stragglers from Started to Completed at sprint end so reports reconcile cleanly.
The bigger picture
Status data is there, status flow is missing
Teamwork models tasks with a clean status lifecycle of New, Reopened, Started, and Completed, plus rich priority and assignee fields. Teamwork for WordPress mirrors all of it into custom tables faithfully, then renders a flat admin list. That gap is where teams lose time, because flow is the thing humans want to see and a list does not show it.
SleekView Kanban groups the same rows by status, shows priority as colored pills, joins to user records so the card front is a sentence rather than a row of IDs, and lets you drag a card to update status. The change writes back through the next sync push so Teamwork itself stays current, and the same board can render on the WordPress frontend for clients or executives without a Teamwork seat. Agencies running their delivery off WordPress get a true project board where their content already lives.
Internal teams get a shared view that pulls them out of dashboards and into doing work. The plugin already does the hard part by mirroring the data, this turns that data into the view it deserves.
Questions
Common questions about SleekView Kanban for Teamwork for WordPress
Mainly teamwork_tasks for the row per card, plus teamwork_tasklists for column names when grouping by list, teamwork_users for assignee labels, and teamwork_projects for project context. SleekView only reads tables the plugin already maintains, never calling the Teamwork API directly.
Yes. Add a SleekView filter on project_id and save it as a named view. Each project gets its own kanban URL, the column counts adjust automatically, and you can layer status and assignee filters on top so leads open straight into their scope without extra clicks.
SleekView writes the new status value to the row in teamwork_tasks and fires the plugin write hook. The next sync push sends the change to Teamwork. The card stays in its new column locally so the team can keep moving without waiting on the API round trip.
Priority appears as a colored pill on the card front, low blue, medium amber, high rose. The card background stays neutral so the column color remains the dominant visual cue. You can also color the column header dot by priority distribution if you want a quick load read.
Yes. SleekView compares due_date to today and renders overdue cards with a rose date pill. The same rule drives an overdue counter in each column header so project leads see how many tasks slipped past their target without opening any individual record.
Yes. Drop the SleekView shortcode on any page and the board renders. Combine the shortcode with a role-based filter so logged-in clients see only their project tasks and editors see the full company board. Drag-and-drop is gated by capability per render context.
Subtasks are stored in teamwork_tasks with a parent_task_id set. By default SleekView treats them as their own cards on the board. Add a filter where parent_task_id is null to show only top-level tasks, or render the subtask count as a small badge on the parent card.
Yes. Reopened is one of the distinct status values in teamwork_tasks, so it renders as its own column when you group by status. Color it rose to make reopened work obvious in the board layout, since it usually means something went wrong on the first close.
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.
Lifetime ♾️
Most popular
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
€749
Continue to checkout