Feature updates
Report current Feature health with authored updates and scoped discussion.
A Feature update is a current-state report for a Feature. It is separate from the Feature's Spec, Plan, Tasks, Build Notes, linked Issues, and roadmap dates, but it can include display-safe context from those planning fields.
Feature Activity
Open a Feature and choose Activity to publish or inspect updates.
Editors can post an update with:
- a health value: On track, At risk, or Off track
- rich update text
- changed planning context shown before posting
- optional discussion through update-scoped comments and reactions
Comment mode in the same Activity surface creates a normal shared Activity comment on the Feature subject. Update replies stay attached to the specific update card, so Feature Activity does not become a general chat room.
Writing and formatting
The update composer uses the placeholder Type / for commands and does not
show a permanent formatting toolbar. Type @ to mention a supported person or
object, or type / for report blocks such as a section heading, bulleted list,
numbered list, quote, or divider. Bullets and numbers remain visible while you
write and after the update is posted. When the / or @ menu is open, Enter
selects the highlighted option without posting the update. After the menu
closes, Cmd/Ctrl + Enter posts the draft; plain Enter continues editing.
Health updates intentionally keep a compact report format. Full-document features such as tables, images, code-block controls, callouts, collapsible sections, and a table of contents are not exposed by the Activity composer; they remain in the Feature's primary document.
The same timeline also records Feature property changes with property-specific icons or changed-person avatars. Status, priority, lead, members, Teams, Initiative relationships, dependencies, dates, schedules, icon color, and labels use event-time display snapshots where available. Label edits are grouped into one row per save, and archived-label deletion preserves the historical label name and color.
Overview and table health
The Feature Overview shows the latest update between Resources and the Summary area. If no update exists and the user can edit the Feature, Integrity shows a first-update prompt that routes to Activity.
The Feature table uses lifecycle health for scanning:
| Field | Behavior |
|---|---|
| Health | Shows the latest authored health or missing/stale update state. |
| Health updated | Shows when the latest qualifying update was posted. |
| Health preview | Opens the latest update body, context rows, comments, and reactions without leaving the table. |
Feature Health filters and grouping use this lifecycle-backed state rather than the old proposal/draft fallback.
Changed context
Feature update context can include changed status, priority, Team, lead, members, labels, dates, Initiatives, and dependency relationships. Context is captured when the update is posted so older updates keep their original evidence.
Hidden generated-context blocks and deprecated Issue or child-Feature movement summaries are omitted from rendered update context.
Permissions
Reading follows Feature visibility. Posting, editing, deleting, and changing schedules require the underlying Feature edit permission. Visible users can comment or react through the shared Activity permissions for that Feature.