.avif)
.png){kind=icon}
.png){kind=icon}
.png){kind=small}
π€« Shhh, Keep It Private (Incidents)
We are excited to release the ability to create incidents as Private.
Common use cases are for security or other sensitive incidents that you may not want broadcast to the entire company.
Whenever a Private incident is triggered, we create a private channel, silence notifications, and hide it in the Web Dashboard.
We give you a powerful suite of features to configure and control access. We also ensure Private and Public incidents can co-exist seamlessly.
- Create Private incidents from Web or Slack
- On a per incident basis, choose if you want to create incident as Private
- Only Rootly admins can see or access on Web Dashboard
- Spins up private incident channel on Slack
- Notifications to your global #incidents channel are muted
- Any Private incidents are tagged with π Private
In Action
π New & Improved
- π New Task in Workflows that allows you to rename your incident channel on Slack
- π Use your Jira ticket number/slug as your incident channel title in Slack - syntax
{{incident.jira_issue_url | split: "/" | last}} - π New coat of paint on rootly.com/demo with detailed walk-through video
- π New Task in Workflows that allows you to change incident states (e.g. auto resolve incident if inactivity for 24hrs)
- π Zoom integration no longer relies on a user credentials to start the meeting
- π Beta features get an appropriate (beta) tag to give customers a heads up
- π Any time selector now includes UTC such as organizational timezone
- π Cleaned up Google Meet UI in Slack to reduce visual clutter
- π Auto resolve setting migrated out of organizational settings and into Workflows
- π Fixed issue where duplicate title names could not be used for Workflow names
- π Fixed issue where scheduled maintenance would incorrectly display warning message to resolve incident
- π Fixed issue where auto archive Slack channels occasionally didn't work
- π Fixed issue where Workflows occasionally did not repeat themselves
- π Fixed issue where action items did not want to be created as Jira subtasks for some customers
