Back to Changelog
Back to Changelog

February 15, 2022

Others

Subscribe to Incidents

Subscribe to Incidents

🔔 Subscribe to Incidents

We are introducing the ability to subscribe to incidents because staying in the loop is critical.

But different audiences want to be updated differently. A couple of examples.

  • Impacted Engineers - want to know every message sent because the details matter
  • Leadership - want to know when the incident is mitigated and resolved, exact details matter less

With the ability to subscribe to incidents, those that just want to follow along easily can do so.

  • Email notifications whenever the incident is Mitigated and Resolved
  • Anyone that enters the incident Slack channel automatically becomes a subscriber
  • Give your organization control to choose how they would like to be updated
  • Ability to subscribe or unsubscribe with a single click


🌝 New & Improved

  • 🆕 Overview when incident Slack channel first created is automatically pinned for easier access
  • 🆕 Ability to unpublish and edit already published postmortems inside of Rootly
  • 🆕 Workflows run sequentially in 1-2-3 order instead of all at once
  • 🆕 View in Linear button added next to any Action Items that are created
  • 🆕 Linear integration in Workflows now support the ability to create incidents in a specific state (e.g. Todo)
  • 💅 Significantly reduced the number of clicks required to quickly edit configurations (e.g. Severity, Services, etc.) by redirecting users back to list view
  • 💅 New and standardized error pages for Web
  • 💅 UI improvements to postmortem tab in Rootly to make it clear when it's editable
  • 💅 New logos on Rootly homepage of customers we partner closely with, we'll periodically rotate them
  • 💅 New coat of paint for rootly.com/blogs with a much more modern feel
  • 💅 Warning message indicating all other login methods will be disabled when SSO is enabled
  • 🐛 Fixed issue where hyperlink in Slack did not redirect you back to the status page after updating
  • 🐛 Fixed issue where images did not render properly inside of Rootly's native postmortem editor
  • 🐛 Fixed issue where searching for Jira project keys did not work inside of Workflows
  • 🐛 Fixed issue where search for Confluence space key did not work inside of Workflows
Previous post
Previous post
You are viewing the latest post

Auto map any user from PagerDuty and Jira to Rootly incidents with new user lookup

Customize Your Incident Overview Banner in Slack

Improved Confluence Retrospective Templates

Workflows Can Now Automatically Update Previously Posted Slack Messages

Automate Component Status Updates on Statuspage.io

Rootly Joins the Vendr+ Marketplace

Assign Multiple Users to the Same Incident Role

Incident Triage: Investigate Potential Incidents Faster

Rootly + Fivetran Data Connector Integration

Less Noise, More Flexibility: New Slack Notification & Emoji Options

SCIM Group Support: Access Control Made Easy at Enterprise Scale

Integrate With External Systems via HTTP Client

Custom Google Doc Permissions

Advanced Slack Customization via Slack Blocks

Notion Projects Integration with Rootly

WhatsApp Integration

Manually Export Action Items to Ticketing Apps (Jira, Zendesk, Linear, and more)

Automated Dashboard Reports

GitHub Secret Scanning Partner

Request for Permission Upgrade

Rootly Joins AWS Marketplace

HashiCorp Vault Integration

Rootly Status Pages V2

Sub-Incidents

Rippling SSO Integration