Get Rootly's Incident Communications Playbook

Don't let an incident catch you off guard - download our new Incident Comms Playbook for effective incident comms strategies!

By submitting this form, you agree to the Privacy Policy and Terms of Use and agree to sharing your information with Rootly and Google.

Back to Changelog
Back to Changelog

October 20, 2021

Others

Saying Hello to Rootly.com

Saying Hello to Rootly.com

๐ŸŒ Saying Hello to Rootly.com

Our Rootly.io domain served us well but its time for a little change. Many of our eagle eyed customers might have noticed we rebranded to Rootly.com over the weekend.

It took us a bit to get this domain but we are officially swapping over. But don't worry. If you've shared Rootly.io links internally and with your customers, they will continue to redirect.

Now that is out of the way, exciting and long awaited features below! ๐Ÿ‘‡

๐ŸŒ New & Improved

  • ๐Ÿ†• Ability to re-order any component (severity, service, role, etc.) inside of Rootly. Now you can display what comes up first!
  • ๐Ÿ†• Introduced a new events system for handling callbacks with third party integrations that dramatically improves reliability
  • ๐Ÿ†• Made clearer in Slack that if you have more than 2 roles that there are more to be assigned
  • ๐Ÿ’… Refactored Confluence and Google Doc to generate prettier docs by default
  • ๐Ÿ’… Pinning items to incident timeline are based on when the message occurred instead of when it was pinned
  • ๐Ÿ’… Create incidents on Web without needing to attach a severity, all fields are now optional similar to Slack
  • ๐Ÿ’… Organizations with over 500+ PagerDuty/Opsgenie users now load faster in Slack when needing to manually escalate
  • ๐Ÿ’… New /rootly tutorial guidance for updating the incident summary
  • ๐Ÿ’… Pinning long messages with line breaks to incident timeline are formatted appropriately instead of one long string
  • ๐Ÿ› Fixed issue where using Functionalities weren't triggering playbooks consistently
  • ๐Ÿ› Fixed issue where postmortems written in Rootly occassionally didn't save correctly
  • ๐Ÿ› Fixed issue where our Workflows weren't checking conditions were satisfied after incident was resolved
Previous post
Previous post
You are viewing the latestย post

๐Ÿšจ Alert Sources

๐Ÿ”” Configurable On-Call Shift Reminders

๐Ÿ“„ Dynamic Forms

๐Ÿ” Granular Role-Based Access Control Settings for On-Call

โœ‰๏ธ Emails as an On-Call Alert Source

๐Ÿ—“๏ธ View Multiple On-Call Schedules Together

๐Ÿค Partial Shift Overrides in Rootly On-Call

๐Ÿ—๏ธ Terraform + API Support for Rootly On-Call

๐Ÿฆ‰ Rootly x Thena Integration

๐ŸŽฌ New Full Platform Tour on Rootly.com

๐Ÿ”ฆ Drop-down Search in Escalation Policy Builder

๐ŸฆŠ GitLab Integration

Update Custom Incident Fields Using Workflows

๐Ÿค– Ask Rootly AI (+ More New AI Features!)

Rootly AI Editor: Fix Typos, Grammatical Errors, and Wordy Text Instantly

๐Ÿ“Š Dashboard Sharing Permissions

โœ๏ธ Customize Your Wordbank for Automatic Incident Title Generation

๐Ÿง  Smart Defaults for Jira

๐Ÿ”Œ The Rootly Plugin for Zendesk

๐Ÿช„ Rootly Retrospectives

โšก Command Palette: Lightning Fast Navigation with a Single Keyboard Command

Rootly Terraformer: Seamlessly Bring Workflows From Rootlyโ€™s UI to Terraform

Smart Defaults for Slack Configuration

Rootly Rewind: Celebrating 2023 With Our Amazing Customers!

Search and Filter Available Actions for Workflows