.png)
.png){kind=icon}
.png){kind=icon}
.png){kind=small}
.png)
We’ve made some exciting updates to the Rootly mobile app to deliver more functionality on the go. Next time you update your Rootly mobile app, you’ll see a newly designed Shifts page which displays your current and upcoming on-call shifts as soon as you open the app.
Caught in a jam without your laptop? No need to send a panicked Slack DM to a teammate for shift coverage. On the shifts screen you’ll see a handshake icon in the upper right corner. You can tap this to easily create overrides right from your phone, either for the full duration of your shift or just a part of it.
Finally, you can also escalate an alert to another responder, service, or team from the Alerts tab of the Rootly app. To escalate an alert, slide it to the right from the Alerts tab in the app, or open the alert and scroll to the bottom of the page. You’ll see a paper plane icon, which you can tap to select the destination you’d like the alert to go to. You can choose from specific responders, services, or teams (or any combination of the three), and specify a title, description, and urgency that will be visible to the recipient of the alert.
Make sure to update your Rootly app to the latest version to enjoy these new features!
🌝 New & Improved
🆕 User Groups can now be auto provisioned with specific Rootly On-Call roles through supported identity provider (e.g. Okta, Jumpcloud, etc.).
💅 Updated Rootly mobile app with a series of visual and UX enhancements.
💅 Permission details for default Incident Response and On-Call roles can now be viewed.
💅 Linear integration now allows users to set Labels when exporting action items manually.
💅 Unified all “are you sure you want to leave setup” modals to a single design to improve UX consistency and predictability across platform.
🐛 Fixed issue with urgency configuration not being applied to incoming Datadog alerts.
🐛 Fixed incorrect alert status being applied to new incoming Cloudwatch alerts.
🐛 Fixed inability to mass remove non-Rootly Slack users from incident channel.
