Incident Preview

🔍 Incident Previews

The vast majority of customers have a global Slack #incident / #outages / #warroom channel.

This is where all incidents get posted for broader visibility.

At a quick glance, we are making it now even easier to know whether or not its important to various stakeholders.

• Dynamic based on impact of incidents to avoid information overload (e.g. if no Service impacted then Service field won't display)
• Shows any impact described at incident creation (e.g. SEV, Teams, Environments, etc.)
• UI easily digestible to know if you should join the incident
• Bold CTA guiding users to join incident channel if relevant

🌝 New & Improved

• 🆕 Ability to duplicate Workflows for faster repetitive automations
• 🆕 Custom date range filters instead of using defaults like Today, Last 7 Days, etc.
• 🆕 Updates to the incident (via /incident update) now get posted as a thread instead of new message in channel for easier access and to reduce noise
• 🆕 GCP added as 3rd party component in status pages
• 🆕 Assigning roles from PagerDuty on-call rotation supports override policies
• 🆕 Roles can now be assigned to the person creating the incident via Workflows
• 🆕 Workflow task to Update Incident (e.g. if incident updated to Security then update visibility to Private)
• 💅 If GitHub integration returns zero commits we still let you know there is 0 commits
• 💅 GitHub repos in timeline are now hyperlinked for easier access
• 💅 After your account is connected with Slack we redirect you back to Rootly
• 💅 Continued infrastructure enhancements to how we handle our Slack slash commands
• 🐛 Fixed issue where emails Workflow did not respect defined formatting
• 🐛 Fixed issue where Google Meet Workflow task had a typo