Changes Feed
The changes feed is a chronological log of every significant edit made to a project. It answers the question “what changed and who changed it?” — without anyone needing to remember to write it down.
What is tracked
Section titled “What is tracked”The changes feed captures:
- Spec page edits — text additions, deletions, and modifications, attributed to the editing user
- Card state changes — approval submissions, approvals, and rejections with timestamp and user
- Card metadata changes — updates to type, members, priority, due date
- Page creation and deletion — when pages are added or removed
- Page renames
Accessing the changes feed
Section titled “Accessing the changes feed”The changes feed is accessible from Project → Progress → Changes. It shows the full history for the project in reverse chronological order.
Individual change batches show what was changed, by whom, and when. For text edits, the feed shows a before-and-after diff of the content that changed.
Why it matters
Section titled “Why it matters”In requirements management, the change history is part of the audit trail. If a Client approved a requirement in week 2 and the spec was modified in week 4, the changes feed shows exactly what changed — making it clear whether the approval still stands or whether re-approval should be discussed.
The changes feed also helps onboard new team members: they can quickly understand the history of a spec without needing someone to narrate it.
Change batches
Section titled “Change batches”Changes from the same user within a short window are grouped into a single batch. This prevents the feed from being flooded by every individual keystroke — it shows meaningful editing sessions rather than character-by-character history.
Why a change doesn’t show up immediately
Section titled “Why a change doesn’t show up immediately”A batch stays open while you’re actively editing the same card or paragraph, so a burst of edits collapses into one feed entry instead of one per save. It only becomes visible in the feed once it closes — after about 5 minutes with no further edits to that specific content.
So after saving an edit, expect a delay of up to ~5 minutes before it appears in the changes feed. This is expected behavior, not a bug: if you keep editing the same content within that window, your changes keep extending the same open batch rather than creating a new one. A hard refresh of the browser won’t make it appear sooner — it truly hasn’t closed yet server-side.