April 29, 2024

AI Summary Variable, Raised Custom Field Limits, User Notification Filters, and more!

AI Summary Variable

AI - Summary Liquid Variable

The latest incident AI summary is now accessible via a Liquid variable {{ incident.ai_incident_summary }}. This means the latest summary, including all the context provided from timeline and Zoom transcript, can be sent anywhere such as other channels, emails, internal status pages, and more.

Let FireHydrant's copilot update your boss so you can focus on the incident!

Raised Custom Field Limits

Custom Fields - Oprah Meme

Currently, multiple organizations within individual accounts share the same global limit for Custom Fields which we set at ten for historical reasons.

We've now raised the custom field limit from ten to twenty for enterprise accounts. We hope this makes it easier for you to track your custom data across all of your organizations!

User Notifications Filters

Users - Notifications Settings Filters

The Users page now allows you to filter users according to which notification methods they've set up. This helps you more easily ensure users don't forget to configure ways to page them

Other Fixes and Improvements

  • 💅 We now send a Webhook event whenever users make any edits to milestones' timestamps
  • 💅 Inbound alerts that match idempotency keys with an existing, open alert within the last 24 hours will now no longer create new alerts. If an existing alert with matching key is dismissed or resolved, or if it's been longer than 24 hours, then a new alert will be opened
  • 🐛 We fixed the "Configure integration" link to actually look like a link on Runbook steps whose integrations haven't been configured
  • 🐛 We fixed a bug where users were unable to subscribe to FireHydrant status pages due to a TLS certificate error
  • 🐛 We fixed a bug with how we handled the indices of alerts that had reached a terminal state, resulting in weird ordering in the alert's timeline
  • 🐛 We fixed an issue where the Jira Runbook step wouldn't correctly assign the Jira ticket if the Runbook was attached manually
  • 🐛 We fixed a minor glitch where clicking on the "Generate" or "Regenerate" button in the Command Center would also collapse the accordion it was on
  • 🐛 We fixed a bug where hitting 'Enter' when searching for Runbook steps, even if there were matches, would result in an exception
  • 🐛 We fixed an issue where users with the maximum number of custom fields would encounter an error when trying to edit an existing custom field

See FireHydrant in action

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

Get a demo