Change History

TruePPM records a change history for tasks, projects, dependencies, sprints, and more. Each edit captures a field-level diff — the old value, the new value, and when it happened — so you can answer “when did this task’s finish date slip, and why?” without a spreadsheet.

Viewing a task’s history

Open a task in the Schedule view and switch to the History tab. You’ll see a reverse chronological list of changes, each tagged with its type:

+ Created — the object was added.
~ Updated — one or more fields changed; the diff lists each field with its old and new value.
− Deleted — the object was removed.

Each entry shows how long ago the change happened. Project admins also see who made the change; Members and Viewers see the change itself but not the user, by design. Long histories paginate with a Load more control.

What is and isn’t tracked

History deliberately excludes CPM-derived fields (early/late start and finish, float, critical-path flag) and sync bookkeeping (server_version, tombstone versions). Those recompute automatically on every schedule run, so recording them would bury the changes you actually care about — duration, status, percent complete, planned dates, assignee, and notes — under recalculation noise.

API

Method & path	Returns
`GET /api/v1/projects/{id}/tasks/{taskId}/history/`	Paginated field-level diffs for one task
`GET /api/v1/projects/{id}/history/`	Project-level field changes
`GET /api/v1/projects/{id}/history/summary/?window=7d`	Aggregate mutation counts by field and object type over a window (`1d`, `7d`, `30d`, `90d`)

Any project Member or above can read history. The identity of the editing user (history_user) is included only for Admins. The summary endpoint is cached for five minutes; pass ?refresh=1 to recompute.

Activity feed (ships in 0.4)

The per-task history endpoint will gain an opt-in ?include= parameter in 0.4 that merges non-diff activity into the same feed:

`?include=` token	Adds events
`comments`	`comment_added`, `comment_edited`, `comment_deleted`
`time`	`time_logged` (scoped to your own entries)
`attachments`	`attachment_uploaded`
`all`	all of the above

Without ?include, the response is unchanged. With it, every entry — including field-diff changes — carries a consistent {event_type, actor, timestamp, detail} shape, and actor is null for authorless or system-generated events. Time-log events are deliberately limited to the requesting user’s own entries, matching the privacy boundary of the time-tracking endpoints.

Retention

History rows are bounded by a nightly purge governed by HISTORY_RETENTION_DAYS (default 90 days). See Outbox & Record Retention to tune or disable it.