A card carries its own record of everything that has happened to it. Open a
card and go to the History tab: every change, every comment, newest first.
This is the tab to open when someone asks who moved this to Proposal?, or
when a value looks wrong and you want to know what it used to be.
What gets recorded
| You see | When |
|---|---|
| updated Dimension | A dimension value changed — the old value is struck through, the new one beside it |
| updated n properties | Several dimensions changed in one save |
| commented | Someone wrote a comment |
| attached a file / removed an attachment | Attachments came and went |
| attached a card / detached a card | A link to another card was made or broken |
| set the card cover / removed the card cover | The cover image changed |
| archived the card / unarchived the card | The card left or came back |
Narrowing the list
The five filter pills at the top narrow it: All, Card updates,
Comments, Attachments, Linked cards. Use Comments to read the
conversation without the noise of every field edit.
The discussion
Writing a comment
Add comment opens a composer at the top of the tab. A comment is markdown,
written in the same editor as a card description — lists, bold and links work
the same way, and typing @ offers the card's own attachments so a comment can
point at one.
Comments live in the same stream as the changes, which is the point: a decision
and the change it caused sit next to each other, in order. "Client pushed the
kick-off to November" reads very differently right above Next step due:
09/10 → 15/11.
Editing, copying, folding
- edit on your own comment reopens it; the comment is then marked edited.
- Copy comment in the row menu puts its text on your clipboard — handy for
pasting into an email. - A long comment is folded, with show more / show less.
Going back
A change that can be reversed — a dimension value, an attachment, a cover, a
link — carries a row menu with two ways back. The card's creation is not one of
them: there is nothing behind it to go back to.
Undo one change
Undo this change reverts that one change and nothing else:
The card goes back to how it was just before that change. Nothing is
erased: the undo is recorded as a new change of its own, and the changes that
came after the one you undid are left alone.
That last part matters. Undoing a Progress change from three weeks ago does
not rewind the deal value you corrected yesterday.
You can add a Reason — optional, but the next person to read the history
will thank you.
Restore the card to a moment
Restore card to this point is the bigger hammer: it takes the card back to
how it stood at that moment.
You choose what to roll back:
- Dimension changes
- Attachments and cover
- Linked cards
- Comments — off by default, and usually best left that way. A conversation
is a record of what people said; rolling it back rarely helps.
Here too, nothing is destroyed. The later history stays, the rollback is
recorded as a new change, and the events it rolled back are shown struck
through.
How undone changes are shown
Once a run of changes has been undone, it stops being interesting, so the
history folds it into a single line — n hidden events — with a chevron to
open it.
Open it and the whole episode is there. Ahmed typed €180,000 where he meant
€18,000; his entry is struck through, marked undone by Laure, and ruled in
red. Just above, in green, sits Laure's own entry marked recovery — the change
that put the value back.
A card's past is never rewritten, only annotated. You can always see what
happened, and that someone corrected it.
Good to know
- The history is per card. A bulk edit across forty cards writes forty
entries, one on each card. - Undo asks for the rights to make the change yourself; Restore asks for
project admin. Rolling a whole card back is a bigger act than correcting one
field, and it is gated accordingly. - A card's history survives the card being archived — archiving is itself
an event in the stream. - Deleting a project's cards deletes their history with them; that one is not
reversible.