Undo and redo

The Planning screen lets you revert your latest changes, then redo them if you change your mind. Unlike a classic undo that would only live in your browser, FoxPlan's undo acts on the project data: it genuinely restores the previous state of the tasks and their assignments.

Accessing the feature

From the planning toolbar:

• ↶ Undo — reverts the last change
• ↻ Redo — replays the change you have just undone

Keyboard shortcuts also work from the planning screen:

Action	Windows / Linux	macOS
Undo	Ctrl + Z	Cmd + Z
Redo	Ctrl + Y	Cmd + Y

In both directions a confirmation dialog appears before anything is applied: an undo is never triggered by an accidental keystroke.

What gets reverted

An undo reverts a complete operation — that is, every change saved by the same gesture, not just the last modified row.

The following are restored together:

• the tasks affected by the operation (dates, duration, name, status, hierarchy, order, etc.);
• the resource assignments belonging to that same operation;
• the child tasks and dependencies affected by the cascade.

Example: deleting a parent task

You delete a parent task containing five child tasks, themselves assigned to resources. A single Ctrl + Z restores the parent task, its five children, their assignments and the dependency links that had been removed.

Covered operations include:

• creating a task or an assignment;
• deleting a task (with its cascade) or an assignment;
• modifying a task: moving or resizing a bar in the Gantt, changing dates, duration, name, status, hierarchy or order;
• modifying an assignment (workload, assigned resource).

Changes made by the AI assistant on your planning can be undone in exactly the same way.

Actuals are never lost

Important guarantee

An undo never destroys a time entry.

Actuals entered by resources (timesheets, activity entry) are carried by the assignments. If you undo an assignment change after a resource has logged time in the meantime, FoxPlan restores the planning but keeps the actuals exactly as they were entered. You can therefore use undo without any risk of wiping the work your team has reported.

Only your own changes

Undo only covers your operations: you cannot revert a colleague's change on the same project, even by mistake.

When undo is refused

Two safeguards protect the consistency of the planning. In these cases an explicit message is displayed and nothing is modified:

• Another user modified the project more recently. Undoing would overwrite their work, so the operation is blocked. Refresh the planning to see their changes before carrying on.
• Changes were made since your undo. Redo then no longer makes sense and becomes unavailable: it would replay a state that has become obsolete.

The Redo button is greyed out

That is the expected behaviour: there is nothing to redo until you have undone something. The ↻ button becomes active after a first successful undo.

Limitations to be aware of

• One gesture = one operation. Grouping is based on what is saved on the server. If an action results in two separate saves — for example creating a task, then assigning a resource to it afterwards — it will take two undos to revert everything.
• Undoing a creation deletes the task. If assignments were added to that task between its creation and the undo, they are left without a parent task.
• Undo applies to the current project, from the Planning screen.

Good practice

Undo is designed to recover from a recent mistake. To compare a planning against a reference state over time, use the baselines described in Planning instead.

See also

• Planning — the toolbar, baselines and auto scheduling
• Copy tasks — duplicate a work package instead of re-entering it
• Project members — who can modify the planning