Plan requirement
| Subscription | Suite Growth or higher |
| Also required | Copilot |
| Access | Admin |
Going back to an earlier version. Useful after a change that made things worse, which is not always obvious immediately.
Restore one
- Open the procedure.
- Look at its earlier versions.
- Compare with the current one.
- Restore the version you want.
- Test before relying on it.
Read the difference first
Restoring undoes everything since that version, including corrections you still want. Compare the two and decide whether you want the old version whole, or one sentence from it.
Often the right move is copying the sentence rather than restoring the version.
Why a change goes wrong quietly
Editing a procedure to handle one awkward case can change the behaviour on the common case. The awkward case is what you tested; the common case is what most tickets are.
That is why the effect shows up as a general decline a week later rather than as an obvious fault.
Write down what you changed
A note per edit, in the description or wherever your team keeps such things. Version history shows what the text was; it does not say why anybody thought that was an improvement.
Change one thing at a time
Three edits in one sitting means you cannot tell which caused the change in behaviour. Slower, and much easier to reason about when something is off.
Test after restoring
The old version was correct against the process as it was. If the process has moved since, restoring reintroduces an inaccuracy that was fixed for a reason.
Comments
0 comments
Article is closed for comments.