Task Due Dates and Reminders

Task Reminders and Due Dates

We're happy to introduce the ability to set due dates for Tasks in FireHydrant. Certain incident tasks need to be completed within a certain amount of time after the incident starts, and with reminders and due dates, you can help ensure responders complete them within the required time.

You will now see due date and time fields when creating or editing Tasks. Once set, you will, by default, receive email and Slack DM notifications and reminders:

• When assigned
• 30 minutes before due
• 10 minutes before due
• When due

Our team is happy to take feedback as we continue to improve our features—feel free to reach out to your Success Managers or Support!

Other Improvements, Fixes, and Deprecations

• 💅 We've reduced the maximum volume for alerts on Android when overriding volume settings
• 💅 Small clarifying updates were made to the warning text when attempting to Archive an incident
• 💅 When an Alert is expired and can no longer be escalated, we've added an indicator in the UI to differentiate it from other open Alerts
• 💅 Our MongoDB event source for Signals has been improved to ingest and pass along more metrics information when opening Alerts in FireHydrant
• 💅 We made additional updates and improvements to the Jira field mapping prompts we added last week to enable creating mappings for required fields more easily
• 🐛 We fixed a bug where "Medium" did not show up in selection dropdowns when setting priority on Alert Rules
• 🐛 We've addressed an issue where the wrong tab was highlighted when navigating to the field mapping tab in Jira project settings
• 🐛 The Lessons Learned tab had issues with overlapping text when the amount of content exceeded a certain threshold. This has been fixed
• 🐛 Jira ticket updates has been improved in Microsoft Teams
• 🐛 When installing Slack for Enterprise grid, we fixed an issue where users encountered a bug with setting default channels
• 🐛 We addressed an issue where notifications were posted into Slack for Milestone updates even when the setting was set to "Threaded only"
• 🐛 Deleted conditions will no longer continue to show up in the Severity Matrix - we remove them automatically
• 🐛 When creating a Follow-Up during an incident, we removed configuration error prompts for projects that are correctly configured
• 🐛 When updating members within a team, the "Last updated" time for the team was not being updated. This has been fixed
• 💥 We will be deprecating the Data Export integration and Data Export page from Analytics - all data will still be available via API, Webhooks, and other means. Please reach out to FireHydrant Support if you are actively using the Data Export capabilities today