Insights & updates from our experts
It is now possible for persons with the Financial Manager or Account Administrator role to relate effort classes to a skill pool. This change was made to limit the chances of specialists selecting an incorrect effort class when registering a time entry. By relating effort classes to a skill pool, only people who are part of that skill pool are able to select those effort classes.

As an example, imagine that Grace Weller, who is part of the Software Architects skill pool shown above, writes a time entry. The effort classes that are available to her are the ones that are not linked to a skill pool, plus the ones that are linked to the skill pool(s) that she is part of.

Frank Watson, who is only in the Expense Reporting Developers skill pool, could then be presented with the Developer-effort classes, and not those intended for architects. This way, the options are reduced for the specialists, avoiding unnecessary mistakes.


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)











