Changelog

What’s new in FireHydrant

Improvement

Okta Network Listing

Nov 21 2022

Okta Integration Network Listing

Bugs and Fixes

  • Fixed a SCIM issue for users reprovisioning with changing email addresses
  • Performance improvements for ingesting alerts from integration partners
  • Fixed an issue where Operational was the default condition when declaring incidents
  • Adding alerts to incidents no longer triggers note specific runbook conditions
  • Fix label and tag grouping in the new command center
  • Fixed issue with Zoom integration where join before host was incorrectly being set
  • Fixed issue with Webex integration where join before host was incorrectly being set
  • Improve performance on the retrospectives page
  • Fix a bug where certain characters were breaking search results
Dylan Nielsen
New

New Retrospectives Experience and default views

Nov 08 2022
Retrospectives

A whole new retrospective experience

  • Today, we're bringing our newly designed retrospective experience out of private beta and into public beta. Taking cues from our redesigned incident command center over the summer, we've made individual retrospective tasks easier to complete, timeline curation significantly simpler, and added a whole new way to add action items during the course of your retrospective.

Incident Participation Statistics

  • Not only did we redesign retrospectives, we're bringing some new functionality as well. When loading up retrospectives in FireHydrant, you'll now be able to see data for the users that participated in that incident broken out by time in incident, starred messages, and actions taken. Empower your retro facilitators to easily find the people responsible for mitigation. As a bonus, this data set is available as template variables for use in any runbook step.

Saved Incident Views

  • A few weeks ago we launched saved views on services. Today, we're opening that up to incidents as well. Now you can save organization wide views for your list of incidents, allowing teams to quickly get back to commonly used filters. As a bonus, you can also set default views so your filtered list is automatically set whenever you visit https://app.firehydrant.io/incidents
Dylan Nielsen
Improvement

Updates on Labels and Tags for Incidents and Improvements for Responding Teams

Oct 31 2022

Updated Labels and Tags in New Command Center

  • For teams using tags and labels for incidents, you’ll now find a simpler way to interact with them in the new command center view. During an incident, you can add any tags or labels that your team will use for breaking down and understanding incidents in the future. Check out the new labels and tags by navigating to any incident page.

Auto Add Responding Teams for Incidents

  • Last week, we launched the ability to add responding teams directly to Slack channels. We’ve now made this team assingment more powerful by allowing you to automatically pull in team members into an incident based on their on-call schedule when an incident includes their service. Check out our guide on managing services and functionalities with teams.
Joel Smith