Preview & Export Retrospectives

An important part of retrospectives is the ability to share them. FireHydrant offers several capabilities to flexibly export incident reviews.

Email Share

When finished with the Retrospective, you can click "Share Retrospective" at the top right. This will open a modal where you can confirm who you'd like to email or share the retrospective with (by default, all assignees on the incident will be included). Once confirmed, the link to this Retrospective will be sent via email.

PDF Export

At the top right, there is always a "View PDF" button available. This will dynamically generate a new PDF document according to the current template being viewed, and this includes all the questions within the template as well as the details and other data shown on the right-hand side.

If there are required fields, a warning will be displayed if those haven't been filled out, but this will not block the user from viewing the generated PDF. This can be useful for previews. Once generated, the PDF can be downloaded with the "Download" button on the top right on the PDF viewer screen.

Confluence

FireHydrant has a Confluence Cloud integration that allows exporting retrospectives and postmortems to Confluence documents. If you haven't already, you'll first need to setup the integration.

Runbook Steps

Once done, there will be two new Runbooks available to you:

• Export Incident Retrospective Template(s) to Confluence - Exports all attached Retrospective templates as configured to Confluence.
• Export Retrospective to Confluence - Exports a specific, configurable template in Confluence's Markdown flavor to Confluence, which is fully configurable and editable within the Runbook step

For most users, the first step to export Template(s) will meet use cases as they directly utilize configured Retrospective Templates settings.

However, for advanced users who want more control, the other step will allow full configuration and control over the template, with Markdown Support and Template Variables support.

Manually-initiated export

Outside of Runbooks, you can also directly initiate an export to Confluence by clicking the ellipses in the Retrospective view and choosing "Export to Confluence." This requires the integration to be installed but does not require the Runbook step.

Google Docs

Like the Confluence export, Google Docs also supports two different Runbook steps:

• Export Incident Retrospective Template(s) to Google Docs - Exports all attached Retrospective templates as configured to Google Docs
• Export Retrospective to Google Docs - Exports a specific, configurable template in standard Markdown to Google Docs, which is fully configurable and editable within the Runbook step

Generally the first step to export Template(s) will meet most use cases, but advanced users who want full control and configurability over what gets exported to Google Docs can use the 2nd step which supports Markdown and Template Variables.

Manually-initiated export

Outside of Runbooks, you can also directly initiate an export to Google Docs by clicking the ellipses in the Retrospective view and choosing "Export to Google Docs." This requires the integration to be installed but does not require the Runbook step.

Webhook & Template Variables

If the above options don't work for you, you can also make full use of Template Variables in Send a Webhook Runbook step.

This step allows you full control over a payload that is sent to any external destination reachable by HTTPS, so this can be used to send any incident data practically anywhere else. For more information, visit the links above.