Back to Changelog
Back to Changelog

January 18, 2022

Others

Severity Descriptions

Severity Descriptions

🦷 Severity Descriptions

What's the difference between a SEV0 and SEV1? Most organizations at best have this defined in an internal doc buried away.

However, that is not much use when you're under pressure and need to quickly create an incident.

We are introducing dynamic severity descriptions that change depending on what severity is picked to provide context.

  • Defined in Rootly > Configuration > Severities > Description
  • Dynamically changes depending on which severity level is picked
  • Reduce top of funnel friction during incident creation
  • Clearly and easily educate your organization on how to define severities


🌝 New & Improved

  • 🆕 Action Items and Tasks have been merged into just Action Items. You can now decide if they are action items you do now (tasks) or do later (follow-ups).
  • 🆕 Mitigated and resolved messages are displayed Slack incident channel for broader visibility
  • 🆕 Integration with Dropbox Paper for postmortem
  • 🆕 User settings are remembered if you toggle between grid or list view in Web UI
  • 🆕 Markdown syntax support for severity description fields
  • 🆕 Postmortems created in Google Docs can be written to shared Drive folders
  • 💅 Invested significantly into scaling our infrastructure and reliability as we continue rapidly onboard customers
  • 💅 Action items Web UI uses tags to indicate priorities instead of sections
  • 💅 Improved our SEO for better discoverability
  • 💅 Renamed Genius to Workflows for specific tasks that run in Slack (that should be them all, goodbye Genius!)
  • 💅 Added sign out link in Slack onboarding flow if users want to restart or use a different account
  • 🐛 Fixed issue where postmortem previews on Web UI dashboard looked incorrectly sized
  • 🐛 Fixed UI issue for connecting Slack accounts to Rootly
Previous post
Previous post
You are viewing the latest post

Paging on Autopilot, Stop Wondering Who is On-Call

We 💛 Google Docs

💌 Sharing Rootly with your Team