New!

[Webinar] Proving ROI

October 24, 2022

Automatically Add Responding Teams to Slack, Updated Teams Management, and Follow-up Items during incidents

Auto Add Responding Teams to Slack Channels

  • When a team has been marked as a Responding Team for a service in FireHydrant, all members of that team can now be automatically added to Slack channels for incidents that connected to that service. To try it out, add a responding team to a service in your service catalog and check the “Auto-add Responding Team” toggle.

Refreshed Teams Management Views

  • We updated the interfaces for managing teams in FireHydrant to reduce clutter and make it easier to understand what services and functionalities are owned by a specific team. You can check out the updated designs by visiting the Teams page as well as viewing any of your teams’ specific pages.

Add follow ups during an Incident

  • You can now create follow ups during an incident in the new Command Center interface. Before, you would have to wait until the retrospective had been started to add follow-up items in Jira or Shortcut. Now, you can those follow-up items as the incident is progressing.

Bugs and Fixes

  • Updated SCIM documentation for API users with correct content-type and added a safe role check and spec to avoid SCIM failing when handling discarded users.
  • Fix for Change Events firing even after Github integration is uninstalled
  • Added exception/logging into Opsgenie API client for better debugging
  • Fixed an issue with the Create Zoom runbook step

See FireHydrant in action

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

Get a demo