History
History lists every change made in a project, newest first, with who or what made it. When a drawing was deleted, a folder moved or the chat reorganized your files and you want it back, undo it from here.
Ask the chat to make a table and save it to the project, then undo a file move the chat made from the History tab.
Open it
Open the project's Tools panel and pick History (under COORDINATION) - "Every change made in this project, with undo". Anyone who can open the project can read its history.
The History tab with a day of changes from people, the chat and a sync
What's listed
Each entry is one sentence saying what happened, with a tag for where it came from - App (a person in Structured), Chat, Sync (a connected app, named), Job (a background job) or Undo - and a line with who and when. A chat entry says who asked, and clicking it shows the request that was typed.
Entries are grouped by day in your own time zone. Click an entry to see exactly what it touched: each drawing, folder or item by name, and what went with it, for example "(41 issues, 12 markups)".
The kinds of change recorded:
- Drawings and folders - drawings added, imported or deleted; folders created, deleted, moved or renamed; drawings moved or renamed; the project's files reordered; files changed by the chat; a drawing's version history changed; an upload cancelled; another project merged into this one.
- Issues - issues deleted or brought back, issue callouts restyled, places of an issue checked off or reopened (see One issue, several places).
- Checks - checks removed.
- Markups and comments - markups or comments deleted, and markup statuses updated after a status list changed.
- Chat - a chat conversation deleted.
- Undos - every undo is itself an entry ("Undid the change to ..."), naming whose change it undid and when.
A few entries say "Made a change" or "Changed Drawings": changes made by Structured's own processing rather than through a named action.
Filter the list
The bar at the top narrows the feed:
- Search names, people and requests - file and folder names, people, and what was asked of the chat.
- Person - Anyone, or one member of the project.
- Source - Any source, or any of App, Chat, Sync and Job.
- Date - Any time, Today, Last 7 days or Last 30 days, or a Custom range with From and To. The tab opens on Last 30 days; if nothing matches, it says which dates it searched and offers Show any time.
- Kinds of change - Everything, or any of Documents & folders, Issues, Checklists, Markups and Comments, plus Deletes only.
The list loads in pages; Load more fetches older changes.
Undo a change
Click Undo on an entry. Expand it first to see what the undo will do:
- "Undo puts back exactly these, as they were at ..." - for a delete, move or rename.
- "Undo removes exactly these" - for something the change added, such as an upload or a new folder.
- "Undo removes the ones this added and puts back the rest" - for a change that did both.
The undo happens as soon as you click. Afterwards the entry says what happened - "Put back: 3 drawings", "Removed: 1 folder" - and its meta line reads Undone. A drawing that comes back brings back what went with it, such as its issues and markups.
Undo only part of a change. When an entry touched several drawings or folders, expand it, tick the ones you want back and click Undo N selected. The entry then reads Partly undone.
Undo an undo. An undo is an entry of its own. Undo it to redo the original change.
What an undo leaves alone
An undo never overwrites later work. If someone changed an item after the change you are undoing, that part is left as it is, and the result lists it under Not put back: with who changed it and when. A few rules keep things as they are too, for example when a newer version of a drawing is now the latest, or an issue has since been merged into another issue.
If the undo would remove work other people did after the change, the result says so ("This also removed work other people did after the change ..."), and you can undo the undo to bring it back.
If an undo would bring back issues that were hidden for some other reason - re-run away by a newer check, merged into another issue, or retired when their document was reprocessed - it stops and asks: "These issues were hidden for another reason. Still bring them back?". Each issue says why it was hidden. Choose Bring them back or Leave them hidden.
An undo that asks before bringing back issues that were hidden for another reason
What cannot be undone
Some entries are listed so you know they happened, but have no Undo button; expand one to see why. Today these are:
- issue deletions and restores, issue callout changes, and checked-off places;
- removed checks, deleted markups and comments, and deleted chat conversations;
- a cancelled upload, a project merge, a change to a drawing's version history, and markup status updates after a status list changed;
- changes made by Structured's own processing ("recorded without an action").
An undo is also refused when:
- the change has already been undone;
- it would bring issues back while QA/QC is frozen on the project, until an admin unfreezes it;
- it would remove drawings and deleting documents is switched off for your organization (your organization's owner controls this);
- part of the change was permanently removed, so it cannot be brought back.
Who can undo
Reading the history needs only access to the project. Undoing is decided by two rules in Organization > Settings > Permissions (see Organization page):
- Who can undo their own changes in a project's history - by default, people who can edit the project.
- Who can undo colleagues' changes in a project's history - asked as well, when the change was made by someone else or by no one (such as a background job). By default, also people who can edit the project. Untick Members to let only Team leads and org owners undo a colleague's change.
Org owners can always undo. Viewers never can.
Undo from the chat
The chat can read the same history: ask "what changed in this project yesterday?" or "undo the move you just made". It asks you to confirm before it undoes anything. If an undo would bring back issues that were hidden for another reason, the chat does not undo it and points you to the History tab, where you can choose.
How long history is kept
There is no time limit. A project's history stays for as long as the project does; older changes are reachable with Any time and Load more.