New Slack /fh learn Command and a Big Shipment of Improvements

Hey there, firefighters 🧑‍🚒 Here's what's shipped for you this week!

🧠 New Slack Command: /fh learn

We've introduced a new Slack command to help your team get up to speed with FireHydrant! The /fh learn command launches a brief tutorial that walks users through basic Slack commands for incident management.

This interactive tutorial is perfect for:

• Onboarding new team members
• Refreshing knowledge for existing users
• Building confidence with the FireHydrant Slack commands

💅 Other Improvements

• Call Routes API: We've unhidden the list call routes endpoint, making it easier to programmatically access and manage your call routing configurations through our API.
• Resilient Signals UI: We've added graceful backoff handling to the Signals UI when loading large numbers of signals, automatically reducing the number of signals displayed to ensure you can still access critical information without errors.
• Transposer Slug Protection: We've disabled editing of transposer slugs after creation to prevent unintended configuration changes.
• Better Form Behavior: Navigation after successful form submissions no longer triggers unnecessary confirmation prompts.
• Filter Incidents by Retrospective Template: You now have the ability to filter your incident overview by which retrospective template was used for your incident.
• Import Error Handling: Now when an import fails, you'll see detailed error information instead of a generic "0 items imported" message, making troubleshooting much easier.
• Microsoft Teams Group Chat Updates: Now when a role is assigned to a user, they will be automatically added to the group chat, reducing the time to involve a responder.

🐛 Bug Fixes

• Fixed an issue where the "Do Not Disturb" override wasn't correctly displaying its status when first visiting the settings page on Android devices.
• Fixed the drag-and-drop functionality for Priorities on the Ticketing Settings page.
• Resolved a bug where the forced time zone setting couldn't be turned off in organization settings.
• We've fixed an issue that was preventing milestone updates after an incident entered the "post incident" or "closed" state.

That's all for this week! As always, if you have any questions or feedback, our team is here to help.