What a task holds
| Field | Notes |
|---|---|
| Title | A verb and an object. "Redirect map" is a noun; "Build the redirect map" is a task. |
| Owner | Exactly one person. Shared ownership is the most reliable way to make something nobody's job. |
| Due date | Optional and load-bearing. Without it a task cannot be late. |
| Section | Its column on the board. |
| Description | What done looks like. |
| Subtasks | One level deep. If you need two, it is a project. |
| Comments | Where the actual knowledge accumulates. |
| Attachments | Files relevant to the work. |
My tasks
7 open · 2 overdue
Due 8 Apr
Due 9 Apr
Due today
Due 18 Apr
Due 21 Apr
Comments are the record
In practice, task comments become the largest store of institutional knowledge a team has — the reason a decision went one way, the constraint somebody discovered, the thing the client said on the phone. That is worth being deliberate about.
- Write the decision, not just the update. "Going with option B because the API rate limit rules out A" is worth more than "done".
- Mention people rather than messaging them separately, so the context stays with the work.
- Paste the relevant part of an email into the task rather than leaving it in a mailbox.
Search
/pm/search covers task titles, descriptions and comments across every project you are a member of, including archived ones. For a question that starts "why did we…", this is usually the fastest answer available anywhere in the suite.
If a colleague can find something you cannot, project membership is the difference, not an index problem.
What this does not do
No timers, no logged hours, no time reports.
A weekly task is created weekly, by somebody or by an integration.
The task shape is fixed.
You can reference another task; nothing moves automatically.
Deliberately. Deeper nesting is a project.
Questions
Can a task have two owners?
No. Add a subtask or a second task.
Can we bulk edit?
Yes, in the list view.
Do completed tasks stay searchable?
Yes, including their comments.