Project
WordPress Task Manager
A WordPress plugin that brings structured tasks into wp-admin: clear ownership, status, and context next to the rest of your site - without standing up a separate project tool. It leans on core patterns - custom post types, metaboxes, list tables, and capabilities - so it behaves like software your editors already recognize.
What does it do?
The plugin introduces a dedicated task model inside WordPress. Each task is a first-class record - not a row hidden in a shared Google Sheet or a sticky note on somebody’s monitor. You capture title, description, status, assignee, due hints, and relationships to content where that matters (for example tying a task to the post or page it belongs to).
The interface lives in wp-admin on purpose. Editors and developers already spend time there; meeting them where they work lowers friction compared with exporting CSVs or switching to another SaaS tab. The goal is not to replace Jira for a fifty-person programme office - it is to give small teams a dependable task list that respects WordPress roles and backups.
Inline screenshots on this page use the same files as the gallery at the bottom: add or replace images under img/projects/wordpress/task_manager_plugin/ to refresh what visitors see.
Workflow and features
Tasks surface in standard admin list tables with filters for status and responsibility where those fields exist. Bulk actions and quick edits follow WordPress conventions, so muscle memory transfers. Metaboxes on the task edit screen keep metadata structured instead of burying JSON in a generic field.
Sane defaults matter: statuses are enumerable, assignees map to real WordPress users, and empty states explain what to do next. The result is fewer “what does this column mean?” conversations and less time spent repairing inconsistent spreadsheets.
- Custom post type (or equivalent) for tasks with editor-friendly fields
- List tables, sorting, and filters aligned with wp-admin habits
- Metaboxes and validation instead of unstructured free text
- Optional ties between tasks and posts/pages where workflows need it
- Capabilities wired so only the right roles can close or reassign work
How it fits WordPress
Implementation follows the WordPress extension model: PHP hooks for bootstrap, admin enqueue for scripts and styles scoped to plugin screens, and the Options or post meta APIs for data that must persist. Where appropriate, nonces and capability checks surround mutating actions so CSRF and privilege escalation stay boring problems.
The database story is plain MySQL through WordPress APIs - no parallel ORM you have to teach operators. That keeps backups, search/replace migrations, and staging clones predictable because tasks live in the same database export as your content.
add_action('init', function () {
register_post_type('task', [
'labels' => $labels,
'show_ui' => true,
'supports' => ['title', 'editor'],
'capability_type' => 'task',
]);
});Who it is for
Small agencies, in-house marketing teams, and maintainers who already live in WordPress benefit most. If your “project management” today is a messy shared sheet, promoting tasks into the CMS often cuts leakage and duplicate effort because assignments sit beside the site you are shipping.
Larger organisations with formal agile tooling may still use this plugin for content-ops workstreams - legal review, launch checklists, and housekeeping that never belonged in a developer-only board.
Quality and compatibility
The plugin aims for compatibility with modern WordPress versions, translation-ready strings, and predictable deactivate/uninstall behaviour. Admin-facing JavaScript stays minimal - enough for metabox interactions, not a second frontend framework living inside wp-admin.
Because the feature set is focused, regression risk stays lower than “kitchen sink” plugins. When something breaks after a core update, the fix is usually localised PHP or a clarified hook priority - not a rewrite of a proprietary task engine.