SleekView for WP Project Manager: projects, tasks & milestones as tables
WP Project Manager (weDevs) stores tasks, milestones, and boards in dedicated pm_* tables, separate from posts. SleekView reads them as flat, filterable, inline-editable tables with cross-project lists, joined names, and pm_meta pivots.
♾️ Lifetime License available
Stop hunting through nested project boards
WP Project Manager takes the principled approach of using its own schema instead of overloading the WordPress posts table. Projects, tasks, milestones, boards, and metadata each live in a dedicated pm_* table with foreign-key columns that link them. The benefit is clean data; the cost is that the plugin's admin UI is project-scoped, so spotting work that crosses project boundaries means clicking through every project in turn.
SleekView reads pm_tasks, pm_projects, pm_milestones, and pm_boards as first-class data sources and joins them so every row shows real names instead of integer foreign keys. A 'this sprint' view spans every project with assignee, milestone, and due date as proper columns. pm_meta gets pivoted on demand: name a meta key like client_tag or billing_status and it becomes a sortable, filterable column. Inline edits write back through the plugin's API where exposed, otherwise directly to the table with an audit log entry.
The view layer doesn't replace the plugin's project pages. Sprint planning, kanban-style board views, and per-project status reports all stay where they are. SleekView adds the cross-project flat list the plugin's design intentionally doesn't ship, the kind of view ops needs to spot stalled tasks no matter which project they belong to. Each view can render as table or kanban so the same data feeds both an ops list and a design lead's status board.
Workflow
From project-scoped boards to cross-project tables
Connect the pm_ tables
Resolve foreign keys
Pivot pm_meta
Save personal views
Sample columns
A typical WP Project Manager tasks view
pm_tasks with pm_projects and pm_milestones so every row shows real names, not foreign-key IDs.
wp_pm_projects + wp_pm_tasks + wp_pm_milestones
| Task | Project | Milestone | Assignee | Due | Status |
|---|---|---|---|---|---|
| Wire Stripe webhook | Billing v2 | Beta launch | alex@studio.co | Apr 28 | In progress |
| Migrate user roles | Onboarding | QA pass | ria@design.io | Apr 27 | Complete |
| Draft client brief | Acme rebrand | Discovery | tom@hello.dev | May 02 | Pending |
| Patch report export | Reporting | Hotfix | mia@brew.coop | Apr 24 | Blocked |
Comparison
Default WP Project Manager vs SleekView
Default WP Project Manager
- Tasks are scoped to a single project view — no cross-project flat list
- Filtering is limited to the current project's milestones and assignees
- Status changes happen one card at a time inside the modal editor
-
Custom
pm_metavalues aren't surfaced in any list - Reporting export is CSV-only and doesn't reflect saved filter state
SleekView
-
Read across
pm_tasks,pm_projects,pm_milestones, andpm_boardsin one query - Inline-edit task status, due date, and assignee across many rows
-
Pivot
pm_metarows into named columns for custom fields - Save filtered views per user (e.g. "My overdue tasks across all projects")
- Switch between table and kanban views of the same task list
Features
What SleekView gives you for WP Project Manager
Cross-project task views
Default Project Manager only shows one project at a time. SleekView gives you a single view that spans every project, with project name and milestone joined as proper columns instead of foreign keys.
Inline-edit assignees and dates
Reassign tasks, push due dates, or flip status from pending to complete directly in the row. No modal, no page reload, no opening every task card during a Monday triage pass.
Filter by milestone, board, and meta
Combine project, milestone, board, status, and any pm_meta field. Save the result as a named view your team reuses, like 'Overdue, billable, not blocked' for an agency capacity review.
Audience
Who uses SleekView for WP Project Manager
Project managers
A single 'This sprint' view across every project, sorted by due date, with assignee and milestone visible at a glance. Status meetings stop being CSV-exports-and-merge exercises.
Individual contributors
'My open tasks' filter scoped to the logged-in user, with inline status updates so progress doesn't get lost between board interactions and end-of-day standups.
Agency owners
Filter by client tag in pm_meta, group by project, and export the visible columns for weekly status reports. Each client gets the slice that matters to them, not a dump of every task.
The bigger picture
Project-scoped tools need a cross-project layer
Project-management plugins are mostly designed for the inside of a single project: this sprint, this milestone, this board. That works for teams running one project at a time and breaks for agencies, in-house teams with parallel initiatives, and anyone who needs a 'what's overdue across everything' answer before a Monday status meeting. WP Project Manager makes the trade-off explicit by storing data in pm_* tables and shipping a project-scoped admin.
Cross-project lists are exactly the layer the plugin doesn't ship because doing so well means joins, filters, and saved views that go beyond the plugin's UI scope. The default workaround is a CSV export per project and a spreadsheet to combine them, which scales badly and dies the moment status changes mid-week. SleekView reads the pm_* tables directly and adds the cross-project list as a saved view, with project names joined and pm_meta pivoted into typed columns.
The plugin still owns project mechanics, kanban transitions, and notifications. SleekView owns the cross-project visibility layer that the plugin's clean schema was waiting for.
Questions
Common questions about SleekView for WP Project Manager
Yes. WP Project Manager (weDevs) uses custom tables: pm_projects, pm_tasks, pm_milestones, pm_boards, and pm_meta. SleekView reads them as first-class data sources, just like any custom table on your site, with the joins between them resolved through the agent UI.
Yes. That's the main reason teams build a SleekView for Project Manager — the default UI is project-scoped. SleekView joins pm_tasks with pm_projects so you can see every task across every project in one flat list, sorted by due date or grouped by status as you prefer.
SleekView writes through the plugin's API where one is exposed; otherwise it writes directly to the table with its own audit log. Status-change hooks and notification triggers fire when the API path is used. For meta updates the API path is generally available; for direct table writes (like custom columns) the audit log captures what changed.
Yes. pm_meta stores per-task and per-project metadata as key-value pairs. SleekView pivots specific meta keys into named columns so a key like billing_status becomes a real, sortable column. The agent UI lists the keys it finds in pm_meta so you don't have to discover them by hand.
Yes. Each view in SleekView can render as table or kanban. For Project Manager that's useful when ops wants a sortable list and the design lead wants a status board, both pulling from the same pm_tasks data. The kanban columns map to status values; reordering and dragging persist back to pm_tasks.
Yes. SleekView is read-and-write on the same tables but it doesn't modify the plugin or its admin UI. Default screens still work as expected; SleekView is an extra surface for teams that need flat, filterable lists. The two coexist: planners use the project pages, ops uses the cross-project views.
If your install records status changes (some setups capture them, some don't), SleekView reads the change log and computes time-in-status as a sortable column. If status changes aren't logged, you can add a custom column populated by an inline edit and sort by it instead, which works as a manual triage signal.
Yes. SleekView reads with cache duration controls so dashboard loads stay fast even with thousands of tasks across hundreds of projects. Indexed columns on pm_tasks (project_id, status, due_date) keep queries cheap. Inline edits scope to the row being edited so write-path concurrency isn't an issue in practice.
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