Making Incident Creation a Breeze

πŸ’¨ 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.

  • /incident will 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 timeline or /incident timeline command
  • πŸ’… 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 + Enter as 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

Rootly helps you respond to incidents faster as a team and learn to prevent them in the future.