Back to Changelog
Back to Changelog

March 7, 2022

Others

Convert Existing Channels to Rootly Incidents

Convert Existing Channels to Rootly Incidents

🧞 Convert Existing Channels to Rootly Incidents

Rootly provides the most comprehensive suite of onboarding tools to help companies rapidly adopt better incident management.

As with the introduction of any tool, you won't always remember to use Rootly for new incidents due to muscle memory.

For the times you forget, we are introducing /incident convert that allows you to turn existing incident channels into Rootly incidents.

  • Continue collaborating on incidents without losing context or stopping your conversation
  • Incident history preserved and no need to manually backfill into Rootly
  • Link to existing incidents if an on-going incident had already been created
  • Prompts to fill in incident details as if you were just creating a new incident (e.g. Severity)
  • Supports private incident channels


🌝 New & Improved

  • 🆕 New coat on paint on Rootly.com with shiny new logos, testimonials, and product features
  • 🆕 Reordering teams in Web reflect the order displayed in Slack create and update incident wizard
  • 🆕 Ability to reorder components on Rootly status page
  • 🆕 Ability to resend invites to Rootly with one click in Organization Members
  • 🆕 New incident variable for {{ incident.roles }}
  • 🆕 Integrations when incidents are created are shown as hyperlinks
  • 💅 Increased number of times we refresh and check for new Slack channels, reminder you can always go to Integration > Slack > Refresh Channels without waiting
  • 💅 Weekly summary emails are now sent Monday at noon instead of Friday end of day, enjoy your weekend!
  • 💅 Playbooks are displayed in two columns instead of one to reduce visual clutter
  • 💅 Continuing major refactoring internally to ensure Slack commands are even more resilient
  • 💅 Removed /incident connect step in /incident tutorial as all new users are automatically prompted to connect
  • 🐛 Fixed issue where removing labels from Jira did not save for some users
  • 🐛 Fixed issue where selecting State in Linear Workflow task did not populate results for some users
  • 🐛 Fixed issue where clicking save on Linear in Integration gave users an error page despite saving correctly
  • 🐛 Fixed issue where postmortem download to PDF was stalling
  • 🐛 Fixed issue where we displayed a duplicate Workflow task for inviting on-call users to Slack channels
Previous post
Previous post
You are viewing the latest post

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

View Who’s On-Call