π£ Beautiful Incident Timeline Pages
We are excited to release beautiful incident timeline pages that can be easily shared across the organization.
Why? Following along incidents can be noisy especially given the amount of collaboration required to debug the issue. Teams such as customer support are left wondering what is applicable to them and often causes confusion leading to more questions.
Incident timeline pages solve that by providing a high level overview of everything that is important that teams can easily follow along.
- Updates to the incident timeline page are pinned automatically with π emoji in Slack
- Updates to timeline in the Web Platform automatically updates the incident timeline page
- Link can be easily shared across the organization to Rootly users
- Executive overview of all relevant information without scrolling around in Slack
- Accessible links in both the incident channel overview in Slack and incident view on the Web Platform
π New & Improved
- π Send Slack Message and Slack Blocks task in workflows now can be sent as ephemeral (Only you can view)
- π Adding responders via Opsgenie and VictorOps now split into users and teams instead of combined for easier search
- π Custom field support for Asana integration
- π Ability to configure assignee for Asana integration
- π Stepped line chart support in metrics
- π Stacked charts support in metrics
- π API support for CRUD custom dashboards in metrics
- π Reworked data model for Statuspage.io integration that will unlock ability to leverage templates and components
- π PagerDuty integration better respects escalation policies and acknowledge events that is aligned with native PagerDuty
- π Infrastructure improvements to better support concurrent incident creation for a single organization
- π Action items in Web Platform grouped by their respective role, playbook, or other if applicable for easier categorization
- π PagerDuty and Opsgenie alerts are automatically closed when an incident is resolved
- π Fixed issue where exporting metrics from specific charts as CSV and JSON did not work
- π Fixed issue where elapsed time on Web Platform was not updating without a refresh
- π Fixed issue in workflows if you set repeat every to 0 it causes an error
Rootly helps you respond to incidents faster as a team and learn to prevent them in the future.