Comments, files, dependencies, and subtasks

Open /tasks/[id] for the complete task record. The detail page centralizes schedule, recurrence, approval, comments, activity, dependencies, subtasks, evidence, and recurring history.

#Comments and watchers

Use Comments for task specific discussion. Watchers receive the task context without becoming the assignee. Add only workspace members allowed to see the task.

Comments and watcher changes remain attached to the task audit trail. Do not place secrets or unrelated sensitive records in a task comment.

#Attachments and evidence

Upload supported files from the task detail. The uploader and assignee can remove permitted attachments, while managers retain administrative control. A file can also be selected as proof where the task workflow supports it.

Use a descriptive filename so a later reviewer understands the evidence without opening every attachment.

#Dependencies

Add a blocking task in the Dependencies tab. The task card shows the number of unresolved blockers. Complete the blocker before treating the dependent work as ready.

Dependencies must link tasks inside the same workspace. Avoid circular chains. If A blocks B, do not also make B block A.

#Subtasks

Managers can add subtasks under a parent. A new subtask inherits the parent assignee unless another assignee is selected. Use subtasks for separately completable work. Use a checklist in the description for steps that do not need their own status or owner.

#Activity and history

The Activity tab records important changes. Recurring templates also expose occurrence history. Use history to answer who changed assignment or status rather than relying on the current values alone.

#Common problems