Tasks Gets Modules, Typed Relations, Saved Views, and Sprint Burndown
Tasks adds four Plane-parity features at once: modules for grouping work, typed dependency relations, per-user saved views, and a real sprint burndown chart.
Tasks has shipped a set of four features aimed at closing the gap with dedicated project-management tools like Plane: modules, typed relations between dependent tasks, saved table views, and a sprint burndown chart — all backed by new D1 tables and live on production.
Modules
Tasks can now be grouped into modules, a layer above individual cards for organizing related work — a new Modules tab in each board lets you create, list, and manage them, and tasks pick up a module through a picker in the task dialog.
Typed relations
Task dependencies used to be a flat, untyped link. Dependencies now carry a relation_type, defaulting to "blocks," so a dependency can express not just that two tasks are connected but what kind of connection it is.
Saved views
The table view's filter bar is backed by real saved views now, upsert-by-name and scoped per board and per user — so a filtered, sorted table layout you set up once can be reopened later instead of rebuilt from scratch.
Sprint burndown
A new burndown endpoint powers an Analytics tab with an actual sprint burndown chart, rather than leaving progress tracking to manual estimation.
Under the hood
Four migrations landed on production D1 for this release (module IDs on tasks, a board-modules table, a relation-type column on dependencies, and a saved-views table), and the tasks worker gained the CRUD routes and vitest coverage — 238 tests — to back all four features. The new saved-views table was also added to the tasks GDPR erasure path, since it's keyed by user ID.
This is a big batch of functionality landing together; expect the UI on some of these surfaces — particularly the Modules and Analytics tabs — to keep evolving as real usage surfaces gaps.