.png)
.png){kind=icon}
.png){kind=icon}
.png){kind=small}
Your incident’s severity determines which playbooks, workflows, and automations your team uses to manage and resolve it. High-risk information might be shared to get your system back online, and with many teammates observing and collaborating, it becomes a challenge to enforce protocol in a safe and secure manner.
Now, with Rootly’s severity-based roles and permissions, you can lock down permissions and capabilities to specific users based on the incident's severity. For example:
- Only Incident Commanders can escalate an incident to SEV1.
- Only executives can send customer communications for SEV0 incidents.
- Only engineering directors can cancecl SEV0 incidents.
Your incident permissions can be defined across a range of dimensions on the incident, including:
- A user's role in Rootly vs. their assigned role in an incident.
- Upgrading an incident's status or severity.
- Setting an incident's types and field values.
- Publishing to a status page, assigning roles, updating the timeline, and more!
Reach out to your account manager to get set up!
🌞 New & Improved
🆕 GitHub pull requests and GitLab merge requests can now be linked to incidents. Updates to the requests are auto-broadcasted in the respective incident Slack channels.
🆕 Added the ability to pass key-value pairs as the details field when creating an Opsgenie alert via workflow.
💅 Improved PagerDuty migration process to include placeholder users for users that have been deleted in PagerDuty but still remain in schedules. This will help maintain rotation order when moving from PagerDuty to Rootly On-Call.
💅 Existing alert notes can now be edited and deleted with the Alert Update permission for On-Call users.
🐛 Fixed text misalignment issue on List of Alerts page on web UI.
🐛 Fixed issue with schedules only being created for two weeks when configured via Terraform.
