Restore previous versions of escalation paths

Have you ever accidentally made a change to an escalation path you wish you could undo? No fret! You can now preview and restore previous versions of your escalation paths.

This should give you and your teams more confidence in how you manage your escalation paths, knowing if someone accidentally makes a mistake or change, it’s very easy to revert back to a previous working version! You’ll be able to see a list of versions, as well as what changed (ie. added a level, added a conditional branch).

Simply head to any escalation path and click on the overflow menu in the top right navigation to make your adjustments.

Polishing up policies

We’ve spent a little bit of time freshening up policies, including:

• "Violations" are now "tasks" - We've softened the language around policy violations to just talk about outstanding or overdue tasks. This should make policies feel a bit friendlier and less corporate!
• More reminders! - Previously we let you configure one warning prior to a task becoming due and by default we only told people about overdue tasks. We now:
  • Let you configure multiple proactive reminders, including both before and after the task is going to be due
  • Show both upcoming and overdue tasks on the homepage in the timeline
• Simpler configuration form - The policy configuration UI has been completely overhauled to make it simpler and easier to understand

Updates to ‘Set an incident timestamp’ workflow step

We have updated the ‘Set an incident timestamp’ workflow step to now take in an optional timestamp value. This means you can now set the timestamp to a fixed time, a variable, or it will default to the current time when the workflow runs. Previously, this step would always set the timestamp to the current date and time.

What else we’ve shipped