Insights & updates from our experts
Xurrent’s Change Calendar has been improved again. These enhancements were introduced specifically for organizations that implement hundreds of changes each week. When they open their Change Calendar without any filtering, the sheer number of planned implementations can be a little overwhelming. So, we made sure that the Change Calendar automatically tries to limit this to the most relevant information.

Now, when you open a change and subsequently use the Actions menu to open the Change Calendar, the filter of the Change Calendar is automatically set to the service that is related to the change. This reduces the number of tasks that are displayed in the change calendar, making it easier to spot possible conflicts for the change.
The same filter is applied when you open the Change Calendar from a task. But in addition to setting the filter to the service that is related to the task’s change, the task also gets highlighted with a blue background. This makes it easier to find the task in the Change Calendar.

Keep in mind, however, that the task will only be visible in the Change Calendar when it is related to a service instance.

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)











