Integration - Component & Template Support

πŸ“‘ Integration - Component & Template Support

We are excited to launch our Atlassian integration with support for components and templates.

Customers will be able to manage all communication updates to Statuspage without needing to leave Slack or fumble around with logins and access.

Fast and transparent communication is crucial for successfully managing incidents. Update Statuspage using /incident statuspage or inside of the Rootly Web Platform.

  • Import Statuspage templates and apply them to any Rootly incident for consistent messaging and speed
  • Publish to multiple Statuspages (e.g. customer facing and internal facing)
  • Separately control what is displayed externally on Statuspage vs. the status of your Rootly incident
  • Individually select impact of Statuspage components (e.g. degraded performance, major outage, etc.)
  • Published updates are automatically shared in the incident Slack channel and incident timeline for visibility

Customers may choose to programatically update their Statuspage by leveraging workflows (e.g. if greater than SEV1 then publish Investigating update to Statuspage).

Getting started:

🌝 New & Improved

  • πŸ†• Ability to convert public incidents to private
  • πŸ†• Create incidents option from Alerts view in Web Platfrom now allow modifying incident details before creation
  • πŸ’… Severity descriptions are shown when running /incident update
  • πŸ’… All workflows by default have Slack Command trigger to reduce confusion for manually ran workflows
  • πŸ› Fixed issue where /incident feedback was not working for some users
  • πŸ› Fixed issue where assigning roles in /incident test was not working

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