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

August 11, 2022

Sandbox Environments

Sandbox Environments

๐Ÿ–๏ธ Sandbox Environments

We are making testing your configurations, workflows, and integrations safer and easier with sandbox environments!

A standalone instance of Rootly connected to a separate non-production Slack environment.

An important consideration was ensuring you can seamlessly switch back and forth between production and sandbox environments that does not require logging in and out. You can do this with our organization switcher (top right drop down).

To get started, let your Partnerships Manager know and we'll provision one for you!


๐ŸŒ New & Improved

  • ๐Ÿ†• Action items are shown on Notion generated postmortems
  • ๐Ÿ†• Scheduled start and end times added to incident timeline page
  • ๐Ÿ†• Attribute for private incident visibility in Rootly API
  • ๐Ÿ’… Ability to click move to reorganize workflows instead of drag and drop
  • ๐Ÿ’… Action items are linked on postmortem tab for easier reference
  • ๐Ÿ› Fixed issue where workflow for Jira subtasks were not being triggered
  • ๐Ÿ› Fixed issue where disabling the automatic creation of incident channels was not respected
  • ๐Ÿ› Fixed issue where roles were not showing up for /incident test
  • ๐Ÿ› Fixed issue where some users were getting invalid triggers error on duplicate workflows
โ† Previous post
โ† Previous post
Next post โ†’
Next post โ†’
โ† Pervious guide
โ† Pervious guide
Next guide โ†’
Next guide โ†’