Project plans, sections, and tasks

The work hierarchy is:

Workspace → Project → Project plan → Section → Task

A project plan is a flexible container, not a prescribed sprint or kanban process. Use separate project plans for a roadmap, operational flow, product area, release, or any boundary that helps the team. In navigation, ToDoddle may label this area To-dos for simplicity.

Sections group tasks and can be reordered, archived, and restored. A section may also apply entry actions when a task enters it—for example setting status, priority, task type, assignee, or archive state. The destination section's configured actions are authoritative. Reordering within the same section does not rerun them.

Tasks hold title, description, kind, status, priority, due date, assignee, comments, watchers, attachments, time, blockers, and linked Context. Kinds include Task, Feature, Epic, Bug, Research, and Action Item.

Tasks may have a parent in the same project plan. Parent relationships show grouping and progress but do not automatically complete or archive children. A task can also be blocked by one active task in the same project; cycles are rejected and completed blockers display as resolved context.

Moving a task across project plans is deliberate and stays within the same project. Parent/child relationships that would cross the plan boundary must be cleared first. Cross-project moves are not supported.