---
title: Project updates and milestones in Venom Tasks
description: An update schedule with reminders and nudges for the lead, "update missing" on the list, the page and Pulse, editing and deleting updates, comments and reactions on them, a summary of what changed, an initiative's feed with its projects' updates, and milestones with descriptions and drag-to-reorder.
section: cloud
order: 131
audience: [user, agent]
sources: [services/nodejs-cloud/lib/tasks/project-updates.ts, services/nodejs-cloud/lib/tasks/project-updates-pure.ts, services/nodejs-cloud/lib/tasks/project-updates-handlers.ts, services/nodejs-cloud/components/tasks/planning/UpdateThread.tsx, services/nodejs-cloud/components/tasks/planning/UpdateSchedule.tsx, services/nodejs-cloud/components/tasks/settings/ProjectUpdates.tsx, services/nodejs-cloud/migrations/0354_tasks_project_updates_v2.sql]
features: []
---

A project's **status update** is a health (on track, at risk, off track) and a few lines of text, posted from the
project's **Updates** tab (⌘⇧U on the project page). [Initiatives](/docs/cloud/tasks-initiatives.md) have the same. This page
covers the schedule that asks for them, what each update shows, and milestones.

## Update schedule {#schedule}

Nothing reminds anyone until you turn a schedule on. There are three places to do it:

- **A team**, at **Settings → Project updates** (`/tasks/settings/updates`): Off (the default), Workspace default or
  Custom. A team's schedule applies to the started projects it owns.
- **A project**, from the project's ⋯ menu → **Update schedule…** (or **Change** above the Updates tab): As its teams
  say (the default), Workspace default, Custom or Never. A project's own choice wins over its teams'.
- **An initiative**, from **Change** on its Updates section: Off, Workspace default or Custom.

The **workspace default** is the cadence the other places pick with "Workspace default". It is weekly on Friday at
14:00 until an owner or admin changes it on the same settings page. Cadences: every weekday, every week, every 2
weeks, every 4 weeks, or monthly (the first chosen weekday of the month), at a chosen hour. The hour is in the lead's
own time zone (the one in their notification settings, else their calendar's, else UTC).

An update counts for the next scheduled time after it: post on Thursday and Friday's reminder does not come; the next
update is due the Friday after. Turning a schedule on starts counting then, so nothing is overdue the moment it is on.
Changing the cadence later counts from the last update, not from the change.

## Reminders and nudges {#reminders}

When an update is due, the project's **lead** (the initiative's **owner**) gets one reminder, "Time for an update on
Atlas", in the bell, and by push or email as their [notification settings](/docs/cloud/tasks-settings.md#notifications) say (the
**Project updates** row: push is on by default, email off). If nothing is posted, a nudge follows one working day
later and another two working days later (Monday to Friday, at the same hour). A daily schedule has no nudges.

The safeguards:

- Only started projects and active initiatives; never a paused, completed, canceled or archived one, and never one set
  to Never. No lead, no reminder.
- One reminder and two nudges per due update, then nothing more until someone posts. Posting (from the page, the API
  or an agent through MCP) moves the next due time, stops the nudges and marks the reminder read.
- A reminder goes out only within the hour it was due. A sweep that missed that hour skips it, so a deploy or an outage
  never delivers a backlog.
- Each reminder is created once, even when several sweeps run at the same moment, and pushed and emailed at most once,
  under the same rate limits as every other Tasks notification.
- The lead must still be in the organisation with Tasks access and able to see the project. Their **Project updates**
  switch, **Pause push and email** and the organisation's push and email switches all apply.
- Updates moved in from Linear count as the last update, with Linear's date and author. They never send a reminder or
  a notification themselves.

## Update states {#states}

A project with a schedule shows how its next update is doing, on the project page, the [Pulse](/docs/cloud/tasks-pulse.md) page
and (where the projects list draws it) the list:

| State | When | Drawn as |
|---|---|---|
| due | the update is due, less than three days ago | the health with a dashed ring |
| late | three days past due, and the last update was not on track (or there is none) | **Update late** |
| missing | three days past due, and the last update said on track | **Update missing** |
| quiet | two scheduled times past due: about three cycles without an update | **Quiet** |
| none | no schedule, Never, or not in progress | the health alone |

An initiative with a schedule shows the same states in the health badge at the top of its page and above its Updates.

Pulse's "overdue" list follows the schedule where one is on. A project without a schedule keeps the older rule: no
update in 7 days.

## Editing, comments and reactions {#discussion}

Each update's ⋯ menu has **Edit** (text and health; the update then shows "edited"), **Hide what changed** and
**Delete** for its author or an admin. Deleting an update deletes its comments and reactions, and the project's health
falls back to the update before it (none, if it was the only one).

Anyone who can see the project reacts with the same emoji picker as issues and comments under an update. Mention a
teammate with `@`. A comment notifies the update's author, everyone who commented on it before and everyone
mentioned, through the bell and their **Comments** notification row. You edit and delete your own comments from their
⋯ menu; an admin may delete any.

## What changed {#summary}

Above the composer, Venom lists what changed since the last update (or the last 14 days before the first): progress
(only when it moved more than two points), scope grown or shrunk, issues completed, the target date and the lead
moved, and milestones completed or added. It is saved with the update and shown on it. Turn **Include what changed**
off before posting, or pick **Hide what changed** later, to leave it out. An initiative's update lists its progress
across its projects, status, target date and owner changes.

An initiative's Updates section has **Include project updates**: its projects' updates join the feed, newest first,
each labelled with its project.

## Milestones {#milestones}

On a project's Overview each milestone shows its completion percentage and progress bar. Click a milestone to show its
description (Markdown, up to 5,000 characters), and add or edit it there. Double-click the name, or pick **Rename**
in its ⋯ menu, to rename it; the date field changes its target date. Drag a milestone by its row to reorder.

Drop an issue on a milestone to move it there: on the Overview's milestone rows, on the milestone bar above the
Issues tab (drag a card from the board), or on a group's header in the plain issue list. The milestones' progress
updates once the issue has moved.

## For agents {#mcp}

| Tool | What |
|---|---|
| `tasks_updateschedule_get`, `tasks_updateschedule_set` | read and set schedules (`scope`: workspace, team, project, initiative; `mode`, `freq`, `weekday`, `hour`) |
| `tasks_projectupdate_create` | post; the answer carries `summary` (`summaryHidden: true` hides it) |
| `tasks_projectupdate_update`, `tasks_projectupdate_delete` | edit or delete an update |
| `tasks_initiativeupdate_update`, `tasks_initiativeupdate_delete` | the same for an initiative's |
| `tasks_initiative_update_list` | `include: "projects"` adds its projects' updates |
| `tasks_updatecomment_list`, `_create`, `_update`, `_delete` | comments on an update (`update_kind`: project or initiative) |
| `tasks_updatereaction_set` | react (`on: false` takes it back) |
| `tasks_project_get`, `tasks_project_list` | each project's `updateState` |

They are in the **planning** tool set. The REST routes are in the [Tasks API](/docs/cloud/tasks-api.md#project-updates).
