Preformatted retros - automatically sent to Confluence
Using FireHydrant’s Runbooks, incident and retro data can be automatically sent to Confluence at any point in the incident lifecycle. For example, the moment you’ve resolved an incident FireHydrant can create a fresh Confluence page with all of the critical incident information stored in FireHydrant. When utilizing Runbook conditions, you can choose the perfect moment to send your FireHydrant retro to a Confluence workspace.
New template variables available to all Runbook steps
While FireHydrant offers a nicely preformatted document to send to Confluence, we have also added a new template variable available to all Runbook steps:
retro variable includes all of your custom retrospective questions, contributing factors, and even starred events in a single object. With the new templating option, you’re able to customize Runbook steps such as email notifications and status page updates with contributing factors, starred Slack messages, and custom retrospective fields to include more context than ever before.