Sandbox Environments
Rootly sandbox environments are standalone instances tied to a separate non-production Slack, so you can safely test configurations, workflows and integrations.
On this page
🏖️ 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!
What else shipped
- 🆕 Action items are shown on Notion generated postmortems
- 🆕 Scheduled start and end times added to incident timeline page
- 🆕 Attribute for
privateincident 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
Related changelogs
Rootly On-call Health
On-Call Health is Rootly's open source project that uses incident, GitHub, and Slack data to spot early signs of on-call burnout and help rebalance rotations.
Mobile App Update: Revamped Shifts, New Nav
The latest Rootly mobile update for iOS and Android refreshes Shifts and navigation, with coverage requests you can submit and accept in the app.
Coverage Requests Just Got Easier
Easily request coverage through Slack and the web when you can’t take your scheduled shift (or part of it).