Undo a reshuffle and schedule notices
Put a committed reshuffle back, see what stops a change from going back, and learn how people are told when their booked time moves.
A committed reshuffle can be undone, and everyone whose booked time it changed is told, both when it’s committed and when it’s undone. This page covers the undo first, then the notices.
Undo a reshuffle#
Where to find it#
- Straight after committing, the confirmation on the cascade preview has an Undo… button.
- Later, open the task that slipped. Its Reshuffles card lists every reshuffle committed for that task, newest first, with what each one did, who committed it and when. Each has an Undo… button.
Check what would go back#
Undo… doesn’t undo anything yet. It opens a list of every change the reshuffle made, each marked with what an undo would do to it now:
| Mark | Meaning |
|---|---|
| Goes back | The change can be reversed. |
| Stays: changed since | Someone has edited it since the reshuffle, so it’s left alone. |
| Stays: already started | The time has started, or would be put back into the past. |
| Stays: old slot taken | Something else is now booked where the block used to be. |
The line above the list counts how many changes would go back and how many would stay. Choose Undo reshuffle to go ahead, or Cancel.
An undo reverses whatever the reshuffle did: moved blocks go back to their old times, blocks it added are removed, blocks it released are booked again, and a changed estimate, due date, assignee, outcome or outcome target date is restored.
How long you have#
There’s no time limit, and no fixed window. Each change can go back for as long as the three conditions above don’t apply to it. In practice, the sooner you undo, the more goes back, because booked time starts and people keep editing.
- Time that has started stays. An undo never puts work back into the past, and never takes away time someone has already begun.
- Edits made since are kept. If a block was moved again by hand, or a date or assignee was changed again, the undo leaves it as it is now.
- A taken slot stays taken. A block can’t go back to its old time if that person has since been booked for something else then.
- A later reshuffle comes first. If a newer reshuffle moved the same booking, the older one sees it as “changed since”. Undo the newer one first.
An undo is best effort: it puts back everything that still can go back and leaves the rest, telling you what it left and why. If nothing can go back any more, there’s no Undo reshuffle button.
Who can undo#
- Owners and admins can undo any reshuffle.
- The person who committed it can undo it when it only moved their own bookings, and didn’t change an outcome date, the assignee or which outcome a task belongs to.
A reshuffle in a project that has since been archived can’t be undone.
Afterwards#
The panel confirms “Reshuffle undone”, with how many changes were put back and how many were left as they were, and each change marked Put back or with its reason for staying. On the Reshuffles card the reshuffle is marked Undone, with who undid it, when, and anything that was left.
Connected calendars update in the background, and the people affected are told.
If some of it couldn’t be put back because of a passing problem, you’re asked to choose Undo reshuffle again to carry on from where it stopped.
Schedule notices#
Who gets one#
A notice goes to each person whose booked time a reshuffle changed:
- one or more of their blocks moved;
- a block was added for them;
- a block was taken off them;
- the task was handed to them.
The same people are told when a reshuffle is undone, with what went back.
Nobody else gets one. In particular:
- the person who committed or undid the reshuffle isn’t told, since they saw it happen;
- AI workers aren’t told;
- you aren’t told when a task of yours is only flagged “due date at risk”, or when an outcome’s date is pushed, if none of your booked time moved.
Where it shows#
My Work. Notices appear in the side column, above Invitations, under the heading Schedule changes. The heading reads Updates when support ticket or knowledge base notices are there too. A notice stays for 14 days unless you dismiss it. Each one shows:
- the initials of whoever committed the reshuffle, the project, and how long ago;
- a one-line summary, such as “Jordan’s reshuffle moved 2 of your blocks”;
- each block that changed: the old time struck through with the new time beside it, New for a block added for you, or Taken off you for one released. The first four are shown, with a link to see the rest;
- a button to open the task that slipped.
A notice for an undo is headed “Reshuffle undone”.
The bell. The same change appears in the bell in the top bar. Opening it takes you to My Work, where the detail is. If you’ve turned on browser notifications, it arrives there as well.
Email. You’re sent an email with the summary as its subject, listing what moved, what’s new, what was taken off you and whether the task was handed to you. Times are written in the workspace’s time zone, and the email says which. If your calendar is connected, it has already been updated by the time the email arrives.
Acknowledge a notice#
Choose Dismiss on the notice in My Work. It’s removed from the list and marked as read in the bell. Dismissing can’t be undone, though the change itself is still visible in your bookings and on the task.
A notice you dismiss before its email is sent doesn’t send one.
Choose how you hear about them#
Under Your profile › Notifications, Schedule changes appears twice: once for browser notifications and once for email. Both are on to begin with. Turning either off doesn’t affect My Work or the bell, which always show schedule changes.
See notifications for the bell, browser notifications and the other emails Projik sends, and My Work for the rest of that screen.