Insights & updates from our experts
Recently, a second view of the change calendar was added, in which potential conflicting tasks of workflows are hidden from view. This allows change managers to get an easier overview of all the open workflows. There are of course many ways to filter the change calendar, and different managers and organizations can all have their own preferences. It is now possible to save these preferences.
Especially for organizations that have many open workflows, the default ‘Change Calendar’ view can sometimes be overwhelming. To their change managers, changes of category ‘Non-Standard’, for example, are much more interesting to review than standard changes. After adding the desired filter, a personal view can now be created by clicking the Ellipses menu and then selecting ‘Save as Personal View…’.

Like any other personal view, it can be defined by adding a name, any combination of filters, and whether it should be the default view.

An AI SRE that knows your incidents
Most AI SREs are pattern matchers trained on public data. They know what a memory leak looks like in the abstract. They don't know that your payments-api has a flaky liveness probe everyone ignores, that the checkout team owns the retry policy, or that the last three "database incidents" were actually cache misconfigurations. That knowledge lives in your postmortems, your Slack channels, and the heads of two senior engineers.

How Long Should ITSM Implementation Really Take in 2026?
Most vendors will tell you ITSM implementation takes six months to a year — but modern, configuration-first platforms have rewritten the math entirely. See what real implementations look like in 2026, and why a long rollout is now a choice, not a given.















.webp)
.webp)


.webp)











