Insights & updates from our experts
Sometimes it is important that a change does not get implemented before a certain date. Change managers can use the ‘Start no earlier than’ field of implementation tasks to specify the moment at which the implementation is allowed to start.
To make sure that the team member to whom the task is assigned does not accidentally overlook the value in the ‘Start no earlier than’ field, a warning is now displayed at the top of the task.
This message is only displayed when the moment specified in the ‘Start no earlier than’ field is still in the future. When the specialist accepts the task, or sets the status to ‘Waiting for…’, the warning changes into an information notification.

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)












