June 20, 2024

Google Calendar Integration, Liquid Templating for Catalog Labels, and more

Google Calendar Integration

Google Calendar Integration

We've officially released the Google Calendar integration. This new integration brings two key features: AI meeting transcription and the ability to easily schedule retrospectives.

You'll find a new integration tile for Google Calendar, and once installed, there will be a shiny, brand new Runbook step: Create Google Calendar Event. This will create an event, but more importantly, a meeting associated with this event and the ability to transcribe its audio. Just like with Zoom, this transcription will feed into your AI summary and AI-generated answers to retrospective questions and other fields. The incident and retrospective pages will also have links to the calendar event once created.

Google Cal Schedule Retro Button

In addition, once the incident is resolved, you'll spot a new button on your Command Center page to "Schedule Retrospective." Clicking this button will take you to Google Calendar's new event page with event information pre-filled, including a link to the Incident/Retrospective and all of the incident's responders present on the guest list! Now, it's way easier to quickly schedule an incident review with all the right folks in just a couple clicks!

Lastly, once the retro has been scheduled, we will also display the date/time it was scheduled for directly in FireHydrant's interface!

Documentation can be found here:

Liquid Variables for Labels

Service Catalog Labels Liquid

Labels have been present on FireHydrant's Services and Functionalities for a couple years now, but we've recently added the ability to access them via Liquid templating.

This is useful for printing out a Service's labels/details in numerous places - for Jira field mapping, to page a team with information, sending out emails, and more! You can access these values by using the following Liquid templating:

{% for service in incident.services %}
  {{ service.labels.LABEL_KEY_HERE }}
{% endfor %}

{% for functionality in incident.functionalities %}
  {{ functionality.labels.LABEL_KEY_HERE }}
{% endfor %}

Other Improvements and Bug Fixes

  • 💅 Alert links are now in a separate section and limited to a maximum of five, with a link to see all alerts in the Linked Alerts tab. The overall result is a cleaner Details panel on the Command Center page
  • 💅 We now support wildcard domains on allowed email senders for Signals Email sources
  • 💅 If retrospective exports (e.g., Google Docs or Confluence) exist on a retrospective, we now add them as easy-access buttons at the top of the retro page
  • 💅 When there are no events starred when you start a retro, we now show a prompt and link to documentation
  • 💅 Retrospectives now auto-save when users navigate between tabs, ensuring that any answers to questions or contributing factors aren't lost
  • 💅 We made several small UX improvements to Jira project configuration: more help text, clearer callouts to field mapping, callouts to authorize with a Service Account, field requirements so you can't choose issue types without status mappings and vice-versa, better field lengths and less crampage, and more
  • 💅 In case Slack becomes unresponsive or there is a connection issue, we've implemented safeguards to prevent users from clicking "Declare" multiple times and subsequently creating multiple duplicate incidents
  • 💅 The header of the Command Center now displays the time the incident was opened, which is separate from the Started milestone time which may be adjusted manually
  • 💅 We now have a new transposer for Azure Monitors so you can receive alerts directly from your Microsoft Azure infrastructure
  • 💅 We've renamed the "Tasks" tab to "Tasks & Follow ups" to provide better visibility to Follow-ups being contained on those tabs
  • 💅 You can now delete Functionalities directly on the Functionalities page instead of going in to each Functionality's Edit page
  • 💅 The Event Logs page now shows icons for each Event designating its Source
  • 💅 While viewing an Event's details in the side drawer, the title and body are now Markdown-enabled to increase readability
  • 💅 We clarified some wording in the modal for adding Follow-up tickets using external URLs
  • 🐛 We addressed a bug where the wrong tab was highlighted in the Retrospective because the check for AI features happened after page load
  • 🐛 We mended a weird issue where buttons would have scrollbars if the user's system settings were set to always show scrollbars
  • 🐛 Minor responsiveness issues on the Change Events page have been addressed
  • 🐛 When generating AI answers to Lessons Learned, we incorrectly showed the loading spinner on Follow-ups too even though we were only operating on Lessons Learned. This has been fixed
  • 🐛 We now gracefully handle condition deletions so that if a Service is using a condition (let's say "Borked") and it's deleted for some reason, the Command Center page doesn't crash and incident updates still work
  • 🐛 We fixed an issue with Email Sources where we were using case-sensitive encoding of IDs when all email clients tend down-case email addresses. This is now case-insensitive
  • 🐛 We mitigated a bug where switching from Incidents and Impacts to MTTX Analytics analytics subpages broke and reset the filtering
  • 🐛 There was an issue where pairing "Declared after" with "Assigned Teams" or "Impacted Teams" filters on the Incidents page returned nothing that has been fixed
  • 🐛 We fixed a bug where invalid dates in filters would break the whole page. Now, the filter won't save if values are invalid
  • 🐛 We addressed a bug where custom working hours weren't respected or used when calculating and inserting shifts in on-call schedules
  • 🐛 We corrected a problem where Jira tickets created from Alert Routing were either overwritten by a Runbook step also creating an incident ticket, or there would be duplicate incident tickets on the incident
  • 🐛 Incident search would produce inconsistent results when the incident name included numbers. This has been adjusted so that when searching numbers, we would not only find incidents whose number matched, but also incidents whose titles include said numbers

See FireHydrant in action

See how service catalog, incident management, and incident communications come together in a live demo.

Get a demo