Activity feed

What's tracked, what isn't, and how the real-time feed lets the team catch up without reading every Slack thread.

Every project has an activity feed that records significant changes. The goal: catch up after a day off without reading every Slack thread. Not a complete event log of every keystroke.

Where to find it

Open any task, area, or release modal. The Activity section sits at the bottom of the modal. It shows every recorded entry for that specific entity, newest first.

The project's overall activity feed (a chronological view across all entities) is on the dashboard.

What's tracked

The following actions create activity entries:

  • Tasks, create, delete, rename, area moves, release moves.
  • Areas, create, rename, archive.
  • Releases, create, delete, rename, set-as-active.
  • Projects, create, settings changes, archive.
  • Invites and members, invite created, member joined, member removed.
  • Exports, CSV exports, PDF exports.

What's NOT tracked

Deliberately not recorded:

  • Task status changes (todo → in-progress → done). These happen many times per day per task. Recording each one would drown the feed; the current state of the task tells you the latest.
  • Description edits. Same reason, small frequent edits. The task's description is a single live document.
  • Inline title edits. Tracked as a single rename event, not as a stream of keystrokes.

If you need a stricter audit trail for compliance reasons, that's an Enterprise feature on the roadmap. The v1 model is optimised for "what changed since I last looked" rather than "every byte ever".

How entries display

Each entry shows:

  • Who did it (display name + avatar).
  • What they did (e.g. "moved task to Auth area", "set release as active").
  • When (relative time, "5 minutes ago", with hover for the absolute timestamp).

Activity entries are recorded server-side in the Activity collection and pushed to every open session for the project over WebSockets, so a teammate's action appears in your feed within ~100ms. Task, area, release, subtask, and Feedback Hub submission changes sync the same way.

If updates aren't arriving, open the same project in two tabs and edit a task in one. If the other doesn't update, check the browser console for WebSocket errors, or confirm your network allows WebSocket upgrades (some corporate proxies block them). A refresh reconnects.

AI and external actors

When the AI bootstrap feature creates a project, the resulting tasks/areas/releases all carry "AI" attribution in the activity feed. When MCP tools mutate state, they record activity under the user whose bearer token authenticated the request, so you can see which integration did what. See MCP server.

What's next

Last updated