The Incident and Component status workflows are now unified in Statuspage, meaning easier incident communication and fewer steps to get status updates to the right people.
When creating a new incident, you’re now asked to flag the components that correspond to that incident. This aims to make sure your page is always an accurate reflection of service health, with all the relevant context. As you work through the incident, you now have the ability to add, remove, or override component statuses levels.
Before this update, incidents and components were both triggered and updated separately, meaning extra steps when juggling status updates in the heat of an incident. Often times, customers would create or update incidents without changing component status, leading to confusion on behalf of end users. The new changes should streamline the entire process and help teams manage incidents faster and more efficiently.
Along with bringing Incidents and Components closer together, you’ll also notice a few updates in the dashboard around things like editing past incident updates, editing individual component information, and tweaking scheduled maintenance.
For more on all of the new updates, check out our knowledge base article. If you have any questions or want to send us some feedback, feel free to get in touch at hi@statuspage.io!