Insights & updates from our experts
Last week, a new field was added to the task templates, making it possible to add a note to an approval task, or make a note required when completing any other (project) task. In the Specialist Interface, this could cause the Approve and Reject buttons to sometimes be grayed out, forcing the approver to open the task in Edit mode. To make it more apparent for the approver whether another action is required, this has now been adjusted.

When an action is necessary before approving or rejecting a (project) task, the Approve or Reject button may be used normally. Depending on the situation, one of the following scenarios can then occur:
When a note is required on approval and the task does not contain a UI extension, a popup appears for the required note.

When the task contains custom fields, the task form is opened in edit mode where the status is already preset to approved or rejected, depending on which button was pressed.

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)












