More Control in Organization Settings, Enhanced Help Command in Slack, and Automated “Closed” Milestone in Runbooks

Hey there, Firefighters 🧑‍🚒 Check our what we’ve shipped for you this week, including more flexible organization settings, improved /fh help commands in Slack, more Status Page flexibility, and more. Check it out 🚒

⚙️ Organization-wide Settings

Take more control of your FireHydrant experience with new organization-wide settings:

Weekly Email Preferences: Choose whether your team receives "Last Week in Incident Response" emails

Timezone Management: Set a default timezone for your entire organization (excluding Slack interactions)

💬 Improved Slack Commands

We've revamped our Slack Help command (/fh help) to make it more intuitive:

• All Signals commands are now included
• Updates to descriptions and titles for greater clarity and organization
• New categorization and updated titles, along with helpful emojis

📖 Milestone Management in Runbooks

For incidents that don’t require a retrospective, it can be easy to forget to change the state of an incident to “Closed.” Within the “Update incident details” runbook step, you will now see the Milestone for “Closed,” enabling you to automate the process of closing out resolved incidents, triggered by time lapsed or other criteria. This ensures no incidents get left in the “Resolved” state and you can more accurately track your incident activity.

📊 Status Page Flexibility

You can now add resolved incidents to your status page, promoting greater transparency with your customers by providing both an accurate record of past issues and how issues have been resolved.

📱Call Route Escalations

It happens – the primary contact isn’t always available at the right moment. Call Routes now support escalation steps when using Direct Connect mode, ensuring the critical call won’t go unanswered. If the primary contact is unavailable, the system automatically tries backup contacts with customizable timeout intervals.

🛠️ Other Improvements

• Within Analytics, you can now click into the list of Incidents that have “No value set” for custom fields
• Google Calendar integration now handles bot-created incidents more gracefully
• Enhanced webhook delivery reporting with more detailed data and failure information
• Improved navigation highlighting and consistent table headers throughout the UI
• The mobile app now displays tags in the alert detail screen
• The mobile app now prompts you if you are missing notifications for the current device
• In addition to updating to the closed state in runbooks, incidents can now be filtered based on when they were closed

🐛 Bug Fixes

• Fixed an issue where status messages were occasionally double-posted in incident channels
• Resolved a bug affecting keyboard usage in our iOS app when sending pages
• Fixed navigation highlighting issues on the Settings page
• Addressed webhook delivery inconsistencies

Stay tuned for more updates! We're always working on making incident management smoother and more efficient for your team.