Give a task an owner, a day and a state
Those three fields are the whole contract. A task with no owner belongs to nobody and a task with no due day is a note.
/
Tasks
Tasks is the to-do side of the work: an owner, a due day, a state — inside a project or standing entirely alone. It is the module most people touch most often.
Try it in the demotasks · 3 tasks
Before you start
- Nothing. Tasks works on its own, which is deliberate — the first thing a new installation can usefully do.
What Tasks does
The to-do side of the work, inside a project or standing alone.
Attach a task to a project, or do not
Standalone tasks are first-class here. Not everything that has to be done is billable work, and forcing it into a project to be tracked is how people end up keeping a private list instead.
See tasks on the calendar
Tasks appear on the calendar beside meetings and events, so the day is one picture rather than three.
Worth knowing
- A task’s due date is a day, not an instant. It means that day where the reader is, which is the behaviour people expect and the reason a task is not a meeting.
What it claims to do
The capability list this guide is written against, unabridged. Nothing above adds to it.
Tasks on the Services page- Tasks with an owner, a due day and a state
- Attached to a project, or not
- Visible on the calendar alongside everything else
Where it connects
The modules Tasks hands work to, or takes it from. Most problems that look like one module are a handover between two.