Insights & updates from our experts
Sorting of Requests within a Change
The order in which the requests that are linked to a change are presented within that change has improved. In the past, the requests would be sorted by their ID. Now they are sorted first by their status and then by their ID.

This improved sorting also affects the sorting of:
- Requests within a problem
- Problems within a change
- Changes within a release
- Requests within a change task
- Problems within a change task
- Requests within a project
- Problems within a project
- Changes within a project
- Requests within a project task
- Problems within a project task
- Changes within a project task

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)











