Optionally Create Incident Slack Channels

πŸ•ΉοΈ Optionally Create Incident Slack Channels

Do all incidents deserve their own Slack channel for collaboration?

Not necessarily. For example, incidents that have been previously resolved and are being backfilled, low severity incidents that don't require collaboration, etc.

Previously, all incidents required an incident Slack channel to be created. Today, creating incident channels has been migrated to workflows that enables granular control of when they should be created.

  • Set Slack workspace where the incident channel should be created
  • Set channel title with support for incident variables
  • Ability to set incident channel as private or public by default


🌝 New & Improved

  • πŸ†• Support for native Google Doc templates - see template example
  • πŸ’… Refreshed product images on Rootly.com
  • πŸ’… Link to incident dashboard from /incident overview
  • πŸ’… Tutorial for creating incident automatically from Jira and PagerDuty alerts
  • πŸ’… Cumulative charts hidden from metrics where it doesn't make sense
  • πŸ› Fixed issue where postmortems in Notion ran into workflow failures when incident timeline reached block limit


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