Liquid Templating Improvements, Additional Fields for Status Page, and More!

Liquid Templating Improvements

We launched a new liquid templating experience to help you when building out runbook steps. You can now browse a list of commonly used snippets to quickly insert a template to your runbook step. And if you really want to dig into the details, there's a new Preview experience that allows you to see how your liquid templating will look with real incident data. This makes it even easier to use liquid templating to create powerful and useful runbooks for your team.

Additional Fields for Status Pages

Following-up on our updated status pages, we've added a few new Incident Fields that you can publish to your status pages. To help folks who are building internal-facing status pages, you can now add direct links to the Incident Command Center in FireHydrant, the connected Slack Channel, and the meeting bridge (Zoom, Google Meet, or Webex).

Markdown support in tasks and task lists

Tasks and task lists are great ways to keep your team focused on the work that needs to happen during an incident. Now, you can create even richer tasks (and lists!) by using Markdown to add context like links and lists. Markdown will be rendered in Slack and in the Command Center so that you can easily get more context about any task.

Filter and Search on Scheduled Maintenances

The Scheduled Maintenances page got an overhaul including the ability to filter, search, and save views. For teams managing a number of scheduled maintenances, this improvements makes it easier to get to the scheduled maintenances that you care most about at any given time.

Additional Bugs and Fixes

• We fixed an issue with inactive teams triggering runbooks conditions
• We fixed an issue with older incidents not updating the channel name
• We fixed a permissions issue that blocked some users from starring events in the timeline
• We fixed an issue where images were not showing up in the retro PDF export