Scheduled Maintenance

🔧 Scheduled Maintenance

Rootly serves as a single pane of glass for incidents and now scheduled maintenance events.

A scheduled maintenance is a period of planned downtime communicated in advance. Like incidents, they share many of the same fields such as title, summary, service impact, and more.

Customers can create a scheduled maintenance event directly from Slack or Web Platform.

Maintenance specific workflows around communication, escalation, and more can be built separate from typical incident workflows.

• Schedule start and end time for scheduled maintenance
• Upgrade a scheduled maintenance to a full incident if necessary (e.g. create incident channel)
• Ability to update status page of scheduled maintenance
• Select impacted services, functionalities, teams, and more
• Maintenances displayed in Rootly are visually different from incidents and by default created silently

What else shipped

• 🆕 Incident variable for {{ incident.action_items }}
• 🆕 Shortcut button for adding action items after an incident is resolved in Slack
• 🆕 Terraform support for custom fields in workflow triggers
• 💅 Attaching Rootly services and functionalities hidden when configuring Atlassian Statuspage
• 🐛 Fixed issue where postmortems still persisted on Rootly dashboard after incident was deleted
• 🐛 Fixed issue where elapsed time on Web Platform was not dynamically refreshing