Insights & updates from our experts
The Time spent field has been moved to a position just above the Save button. The advantage of this new position is that people can review the information they have added to a request, problem or task, then enter a value in the Time spent field, and finally press the Save button.

It ensures a more logical flow, because people tended to scroll up to the Time spent field after they had written something in the Note field and then they would scroll down again to press the Save button.
In addition, the Effort class field has been moved to the left so that it is closer to the Time spent field and thus easier to move the mouse cursor over it after the mouse was used to place the cursor in the Time spent field.

The Effort class field appears when a value has been entered in the Time spent field, provided that effort classes are defined for the organization of the person who filled out the Time spent field.

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)











