Update and Re-Export Your Retrospectives

Hey there, firefighters šŸ§‘ā€šŸš’ Here's what's shipped for you this week:

šŸ“¤ Update and Re-export Your Retrospectives#update-and-re-export-your-retrospectives

Keep your retrospective documentation in sync, even after changes.

Teams often need to refine their retrospectives after initial discussions — adding new insights, clarifying action items, or switching to a different template format. But once exported, those external documents were frozen in time. Not anymore!

What's new:

  • Re-export updated retrospectives: Make changes in FireHydrant and export a new version of your completed retrospectives.
  • Repeatable export steps: Execute retrospective export runbook steps multiple times to update documentation across platforms
  • Cleaner UI: All exported links now appear in a tidy dropdown menu for easy access

Why it matters: Your retrospective is a living document. Now when you add that crucial insight during the review meeting or realize you need to use a different template for leadership, you can update the retrospective in FireHydrant and push those changes everywhere ensuring you have the latest version in Confluence and Google Docs.

šŸ› Bug Fixes#bug-fixes

  • Fixed Slack notification spam when importing threads: Users no longer receive @-mentions when importing Slack threads to incidents, instead of getting bombarded with notifications for every message they posted. No more 50+ notifications flooding your Slack activity feed!
  • SSO default roles now work with SCIM: Fixed an issue where SCIM-provisioned users weren't getting their assigned default roles. New team members will now get the right permissions from day one.
  • Better PDF formatting for retrospectives: Multi-line numbered lists in retrospective PDFs now display correctly eliminating formatting confusion in your exported documentation.
  • Improved page load stability: Fixed runtime errors that were occurring during page loads - pages now load reliably without crashes.
  • Smarter Slack link handling: FireHydrant no longer unfurls its own links when posting to Slack channels, keeping your incident updates clean and compact.
  • Coverage gap notifications: Fixed the notification options dropdown that wasn't loading properly so you can now select who to notify about schedule gaps.
  • Runbook template creation: The last step no longer disappears when you click "Save and Continue" so all of your configuration work gets saved properly.

That's all for this week! As always, if you have any questions or feedback, our team is here to help. šŸš€

See FireHydrant in action

See how our end-to-end incident management platform can help your team respond to incidents faster and more effectively.