🫗 Backfill and Import Past Incidents
Inevitably there will be incidents captured outside of Rootly, for example, an outage that lasted a few minutes that was automatically resolved due to self-healing that was in place.
However, it is still important to track it for posterity. We are launching the ability to Backfill and Import past incidents.
- Does not trigger workflows that normally would when incident is created
- Reflected appropriately in metrics with modifiable timestamps for accuracy
- Enable or disable ability to Backfill via Configuration > Form Fields
- Supported via API
🌝 New & Improved
- 🆕 Live on Launch YC
- 🆕 Workflow trigger for Slack channel created
- 🆕 6 min demo overview on Rootly
- 🆕 Workflow trigger and incident variable for whenever a new user joins the incident Slack channel,
{{ trigger.user.slack_id }}
- 🆕 Ability to update role based tasks from Terraform
- 🆕 Ability to edit Slack Blocks from Terraform
- 🆕 Ability to edit action items from Terraform
- 🆕 Download metrics dashboard as PDF and email reports via workflows
- 💅 Terraform errors surface exception message minimizing need to dive into logs
- 🐛 Fixed issue where some PagerDuty accounts were failing to authenticate
- 🐛 Fixed issue related to Terraform schema
- 🐛 Fixed issue where
Update PagerDuty Incident
task would auto-populate title field - 🐛 Fixed issue where for some users they were listed as a subscriber of an incident twice
- 🐛 Fixed issue where some workflows were running delayed
- 🐛 Fixed issue where case insensitive slugs caused 500 errors
- 🐛 Fixed issue where status page updates on Rootly were double posting
- 🐛 Fixed issue where date picker was handling timezone incorrectly
- 🐛 Fixed issue where workflow versions had empty changed by field for some users
- 🐛 Fixed issue where most recent incident was listed second not first for some users on Web Platform