Insights & updates from our experts
Sometimes organizations don’t just want to know the duration of a complete change, but also the duration of each of their separate tasks. For changes that consist of several tasks, two reports were created a few months back, presenting data about the completion duration of the individual tasks. It was already possible to retrieve the resolution duration of tasks using both the Xurrent GraphQL API (resolutionDuration field) and the Xurrent Export API (Resolution Duration column). Now it also possible to retrieve the resolution duration (resolution_duration) using the following REST APIs:
- Requests
- Problems
- Changes
- Tasks
- Projects
- Project Tasks
- Risks

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)











