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


Rootly helps you respond to incidents faster as a team and learn to prevent them in the future.
wave