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

πŸ₯Έ Sync On-Call Schedules with Slack User Groups

πŸ•΅οΈβ€β™€οΈ /rootly lookup: Find and Filter Recent Incidents in Slack

πŸ‘―β€β™€οΈ On-Call Shadowing

πŸ”Œ Generic Webhook Alert Source

πŸ”’ Lock Individual Workflows

πŸ¦β€β¬› Round Robin Escalation Policies

🚨 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