Dear customer,
Thank you for the detailed review. It is great to hear that Dynatrace, Grafana/VMAlert, and Slack were connected in an afternoon, and that schedules, escalations, and per-team and per-severity routing are carrying on-call across your clusters. Keeping most of that work in Slack is what we want that integration to do.
On chained routings: each routing now has a History tab, and each incident has Routing rule executions in the Properties sidebar. Both show which routing and which rule ran, the outcome (executed, delayed, or discarded), and what actually changed on the incident, so you can see which routing won without testing by hand. On the Advanced Routings list you can also drag routings into a custom order so they run top to bottom. Skip subsequent rules still applies inside that routing, after a matching rule. https://docs.allquiet.app/advanced/routing#routing-execution-history-history-tab and https://docs.allquiet.app/essentials/incident#incident-details-routing-rule-executions
Unfortunately, the Jira connection requires Atlassian OAuth, so that integration itself needs to be finished via the Web UI. Routing rules can be exported in Terraform format from the routing editor.
Since this review, the calendar also has a Timeline view, on-call history, and an Effective Schedule that shows who is actually on-call after overrides: https://docs.allquiet.app/essentials/escalations#effective-schedule-vs-detailed-schedules
We hope these improvements and hints will help.
Your All Quiet Team
