Item History & Undo
Item History & Undo records every change made to a Mission Control item — the field, the old and new values, and who made it — and lets you reverse a single change or roll the item back to an earlier point. Nothing on a board changes without an entry here.
On this page
What it is
Item History & Undo is the audit trail behind every board item. Whenever an item's own field or one of its column values changes, Omniscio writes a history row capturing the field, the old value, the new value and the actor, then shows that row in the item's History tab.
The actor is recorded as one of a fixed set of kinds — a person, an agent, an automation, an import, the API, a sync, or unaudited for a mutation that arrived with no actor context at all — together with the actor's id and the id of the session that made the change. That pairing is what answers "which session moved this item?" later.
The switch is pmItemHistoryEnabled, on by default and listed in Settings → Lab.
Where to find it
- A board item's History tab shows the newest changes (50 at a time) with an actor badge, the old value, an arrow, and the new value; each undoable row carries an Undo button.
- Ctrl+Z inside the board reverses the most recent undoable change for that item.
- The same tab's rollback flow previews what a point-in-time rollback would change before it is applied.
How it behaves
Every change, attributed
A history entry records the field name (or the column id for a column value), the old value, the new value, and an actor context: actorType, actorId, sessionId, and where relevant the session turn, a bulk-action id and a cross-board correlation id. Column types flagged as PII-bearing are redacted before they are written, so a history entry never becomes a way to read a value the item itself hides.
If a history write fails, the change still lands — boards are never blocked by their audit trail — and an alert titled "A board change is missing from its history" is raised instead of failing silently. That alert clears itself on the next successful write.
Undo and rollback
- Undo reverses one entry: a field reverts to the entry's old value, or a column value is written back to it, and the reversal is itself recorded in history. Undoing the same entry twice is refused.
- Rollback takes a point in time, plans the field and column changes needed to return the item to that state, and applies them. The plan is capped at the newest 1,000 history entries so planning memory stays bounded.
Synced boards write through the Mission Control API first and mirror the result locally; local-only boards write directly. Undo and rollback are deliberately not transactional across a whole plan: if the API fails partway, the changes already applied stay applied and the caller reports how many landed, so a partial revert is visible rather than silently "done".
Retention
History is kept for 180 days (HISTORY_RETENTION_DAYS) and swept on a schedule; entries for deleted items are purged on their own grace window. Actor and session identifiers inside a history row follow the shorter 90-day retention used across board events.
Related
Boards, items and sharing are described in mission-control.md and mission-control-part-2.md, and comments on items are in mission-control-part-3.md. The multi-step sign-off that writes into this same timeline is pm-approval-workflows.md. Every other page in this library is listed in INDEX.md.
Last verified 2026-11-10