Tasks
Tasks are the breakdown layer inside a project: each task carries a status, a priority, an assignee, an estimate, and a due date — so a project isn't just a bucket of hours, it's a board of work you can prioritise, assign, and track.
Open a project from Projects, then go to Projects → project → Tasks to see its task board.
What you'll learn
- Add tasks to a project
- Task statuses and priorities
- Assigning, estimating, and ordering tasks
- Logging time against a task
Add a task
- Open the project and go to its Tasks view.
- Create a task with a title.
- Set priority, assignee, estimated hours, and due date as needed.
- The task joins the board in order under its project.
Tasks always belong to a project — create the project first, then break it down.
Task statuses
| Status | Meaning |
|---|---|
TODO | Not started |
IN_PROGRESS | Being worked on |
IN_REVIEW | Done pending review |
DONE | Complete |
CANCELLED | Won't be done; kept for the record |
Update a task's status directly from the board as work moves. Completed tasks feed the project's task-progress numbers on the project detail page.
Priorities
| Priority | Use for |
|---|---|
LOW | Nice-to-have; do when the board is clear |
MEDIUM | Normal work — the default |
HIGH | Should be picked up next |
URGENT | Drop-everything items |
Priority is a sorting signal for you and your team; combine it with reordering (drag tasks into the order you want) to keep the board honest about what's next. The order you set is saved.
Assignees and estimates
- Assignee — who owns the task. On a team project, assignment makes the board a lightweight plan of who's doing what.
- Estimated hours — your effort guess for the task. As time is logged, the task's tracked hours accumulate alongside the estimate, so over- and under-estimation is visible per task, not just per project.
- Due date — when the task should land.
Logging time against a task
When you track time — via the timer or a manual time entry — pick the project and the task:
- The entry attributes to the task; the task's tracked hours update.
- The hours roll up into the project's tracked hours and budget burn.
- Task-level tracked-vs-estimated tells you which parts of the project are eating the budget.
Pomodoro sessions can also reference a task, so a focus block counts toward the specific piece of work it protected.
Tips
- Keep tasks small enough that
IN_PROGRESSmeans something — a task that stays in progress for weeks is really several tasks. - Estimate every task, even roughly. Task-level tracked-vs-estimated is where scope creep first becomes visible.
- Use
CANCELLEDrather than deleting — it preserves the decision trail without pollutingDONE. - Reorder the board at the start of each week; the top of the list should always be what you'd start next.
Next steps
- Projects — the container tasks live in
- Budgets and billable time — how task hours become budget burn
- Timer — track time against a task as you work