Split work into subtasks and checklists
Use subtasks when a piece of work needs its own task identity and optional due date. Use checklists for lightweight items inside one task. Both affect task completion: incomplete related items prevent the parent task from being completed.
Record dependencies
Link tasks as blocks or blocked by to show sequencing. These links are reciprocal, so the relationship stays visible from both tasks. Remove or change a dependency when the work sequence changes.
Add reminders
Set a reminder for a task using a date or a date and time, optionally with a note. Use the project timezone convention established in the account settings when planning reminders.
Attach supporting files
Add attachments to the task when they belong with the work. Attachments follow the project’s storage allowance. Inline media used in task descriptions, comments, and notes is served through signed media URLs.
Choose the right control
Use a subtask when the work needs its own task identity, assignee, or optional due date. Use a checklist item for a lightweight verification step. Use a dependency when completion must wait for another task; do not rely on a comment alone for a hard sequencing rule.
Owners, admins, and members can change active task details. Guests can watch a task but cannot edit it or upload files. If an upload fails, check both the active role and the project owner’s storage allowance. Remove a stale reminder or dependency from the task rather than expecting task completion to ignore it.
Related: Tasks, Time tracking, and Attachments.