Insights & updates from our experts
The ‘Copy note to change‘ option was introduced a few years ago. It is a helpful feature for specialists to inform the manager of a change about the information they are entering in the Note field of a task. But when a change manager reviewed the Notes section of a change, it was not always obvious where each of the notes came from.
To clarify this, the source of a note is now visible in the change whenever a note was copied from one of the change’s tasks.

A similar declaration of the source is also displayed in grouped requests after a note was copied from the request group.

This has also affected how notes that were added by an automation rule are presented. A distinction is made between new notes that are created by an automation rule, versus notes that an automation rule copied from another record.
When a note was created by an automation rule, the large automation icon is displayed with the text ‘Automation’ in the note’s header. But when an automation rule copied a note from another record, the creator of the original note is shown and a small automation icon is added.


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)












