Create incidents from Slack emoji reactions, including incident types

We've added the ability to create incidents directly from emoji reactions in Slack. This feature also supports specifying incident types during creation.

Key details:

• Users can now trigger incident creation by reacting to Slack messages with customizable emojis
• Incident types can be specified as part of the emoji-based creation process
• Streamlines the incident creation workflow within Slack

Benefits:

• Faster incident reporting
• Increased flexibility in how incidents are initiated
• Improved integration between Slack communication and incident management

How it works:

• Specific emojis can be configured to trigger incident creation
• Different emojis can be set up to create incidents of various types
• Reacting with a designated emoji automatically starts the incident creation process

This feature enhances the seamless integration between everyday communication in Slack and our incident management system, allowing for quicker and more intuitive incident reporting.

To learn more, view our documentation

User Interface Improvements

We are excited to roll out several UI improvements aimed at enhancing the user experience across various screen sizes and improving clarity in several areas of our application. Here’s a breakdown of what’s new:

Incident Types

• Preservation of Existing Names: Existing incident type names are no longer overwritten when loading.
• Terminology Update: The 'name' field has been changed to 'incident name' in the incident settings page for better clarity.
• Responsive Design: The incident settings page now boasts enhanced responsiveness, with the last few fields wrapped in an elegantly designed card.

User Account

• SSO Account Display Email: We've added a read-only display email for SSO account users, making it easier to identify your account details.
• Mobile Responsiveness: The user account page is now fully responsive on mobile devices, ensuring a seamless experience on the go.

Slack Configuration

• Improved Spacing and Mobile Responsiveness: We've made adjustments to improve spacing and ensure the configuration is user-friendly on mobile devices.

Filters

• Renamed Date Filters: For better clarity, date filters have been renamed to 'Started after' and 'Started before.'

Incident and Retro Pages

• Enhanced Mobile Responsiveness: Both the incident and retro pages have received updates to improve their mobile responsiveness and resolve any existing layout issues.

These updates reflect our ongoing commitment to improving the FireHydrant platform and making it more user-friendly for our valued customers.

Other Improvements and Fixes

• 💅 We've streamlined your mobile experience! You can now acknowledge or escalate alerts on iOS and Android without confirmation, allowing for quicker responses to critical situations. Update your app today to enjoy this time-saving feature.

• 💅 We've improved the way long conditions display in the Execution Rules section. Now, all text wraps neatly, making it easier to read and understand your complex rules at a glance.

• 💅 Our AI just got more intuitive! Incident summaries now factor in the current milestone, giving you more relevant insights as your incident progresses.

• 💅 We've made the "Invite scribe to meeting" step repeatable, ensuring your scribe is always there when you need them.

• 💅 You can now use relative time for partial shift coverage. Need someone to cover "for the next hour"? Just type it in – no more calculating end times.

• 🐛 We've fixed a bug affecting MS Teams users. You'll now see all incident updates in your non-incident channels, even without a specific incident channel. Stay informed without the extra setup.

• 🐛 We've fixed a pesky bug that was blocking some reauthorizations. Now, entitlement checks only run for new integrations, not reconnections. Existing integrations will reauthorize smoothly, even if you've hit your limit.

• 🐛 We've fixed a bug that prevented users from deleting priority on the incident form. Users can now clear the priority field in incident forms. Just select the 'x' option in the dropdown menu.