Templates & activity
This page covers two things that make tasks faster to create and easier to trust: templates for work you do over and over, and the activity feed that records everything that's ever happened to a task.
Task templates
A task template captures a repeatable task pattern so you don't rebuild it from scratch every time. When a kind of task recurs — an onboarding checklist, a release task, a standard request — save it as a template and spin up new tasks from it in seconds, with the structure already in place.
Good template candidates
Anything you find yourself recreating with the same shape — same subtasks, same description scaffold, same checklist — is a candidate for a template.
The activity feed
Every task carries a complete activity feed — a chronological record of what changed, when, and who did it. It's the task's audit trail, and it captures a rich set of events, including:
- Lifecycle — task created, status changed, completed, reopened, reordered
- People — assignees added or removed, watchers added or removed
- Fields — priority changed, due date set, changed, or removed
- Subtasks — created, completed, or deleted
- Discussion — comments added, replied to, liked, or deleted
- Files — attachments uploaded or deleted
Because actions taken by the Associate are logged here too, the activity feed gives you a single, honest history of a task — whether a change came from a person or from AI.
Archiving & reopening
When a task is finished with, it can be archived — tucked away (into the project's docs hub) so it's out of your active views without being lost. Archived tasks keep their full history and can be reopened later if the work comes back. Completed tasks can likewise be reopened, which clears their completion timestamp and brings them back into the active workflow.
Ask the Associate
Beyond reusing templates, the Associate can generate a document from your project's real activity — a status report for a stakeholder meeting, say — delivered ready to share.
Next
Last updated: 2026-05-31
.png)