.png)
.png){kind=icon}
.png){kind=icon}
.png){kind=small}
π¨ Making Incident Creation a Breeze
Whenever customers adopt Rootly, our name quickly becomes synonymous with the easiest way to create incidents.
Today, we are making incident creation even easier by introducing a new slash command /incident on Slack.
/incidentwill function exactly the same as/rootly- Both slash commands can be used at the same time and interchangeably
Why did we do this? Although /rootly was great, many organizations that had a homegrown bot had already defaulted to using /incident.
Not only is it more intuitive, it also means less behavioural changes for our customers which is critical to adoption!
π New & Improved
- π Workflows for PagerDuty now support paging escalation policies in addition to schedules and individuals
- π Customers who use VictorOps can now create Workflows to page
- π Ability to pin more file formats to incident timeline
- π Add events to incident timeline in Slack with
/rootly timelineor/incident timelinecommand - π Improved Web UI for action items so at a glance much easier to see what is open
- π Assigning users for action items are now ordered alphabetically
- π Integrations when configured prompt users to navigate to Workflows to complete their setup
- π
Adding items to incident timeline from Web users can use
Ctrl + Enteras a keyboard shortcut - π Invested into additional monitoring for the Web platform and integrations
- π Relaxed rate limit requirements for bulk updates and configuration
- π Fixed issue where PagerDuty did not page the Admin who originally configured it in Rootly
- π Fixed issue where incident timeline occasionally displayed the incorrect date, one day in advance. Yes timezone is hard
- π Fixed issue where occasionally Workflows did not trigger on incident update but did on incident creation
