Projects
Projects are higher-order groupings of related tasks. Use a project when a piece of work is too large or multi-part to track as a single task.
Projects vs tasks
| Use a task when... | Use a project when... |
|---|---|
| The work is one discrete action | The work spans multiple steps or people |
| It takes less than a day or two | It spans days, weeks, or months |
| It doesn't need independent budget tracking | You want to track scope, cost, or schedule |
| Steps don't need their own due dates | Individual steps need separate due dates and assignees |
Creating a project
- Go to Projects and click New project.
- Give it a name and optionally add a description, target date, and cost estimate.
- Add tasks to the project from the project detail page, or link existing tasks.
Project fields
| Field | What it means |
|---|---|
| Title | The name of the project |
| Status | active, paused, completed, or cancelled |
| Owner | The person responsible for the project overall |
| Target date | When the project should wrap up |
| Budget estimate | Expected total cost (useful for home improvement projects) |
| Actual cost | What you've spent so far |
| Notes | Project context, decisions, links |
Adding tasks to a project
On the project detail page, use Add task to create a new task linked to this project, or link an existing unlinked task using the search field.
Tasks in a project still appear on the main Tasks list — the project view gives you the grouped perspective.
Project progress
The project detail page shows a progress bar based on the ratio of completed to total tasks. When all tasks are done, you can mark the project complete.
When not to use projects
Don't create a project just to group tasks with a common theme. A project makes sense when you need to track overall progress, coordinate multiple people, or manage a budget. For simple groupings, use task tags or context modes instead.