Insights & updates from our experts
Show Related Note in Time Entries
When someone has entered a value in the Time spent field of a request, problem or task and this person subsequently presses the Save button, then a new time entry gets generated for the amount of effort that was specified.
Apart from specifying a time spent, the person may have also added a note to the request, problem, change task or project task.

If that is the case, the time entry that is generated will now be linked to this note. The note is presented in the time entry when it is opened.

When the note is presented in the Notes section of the record to which it was added, the header indicates the time spent of the related time entry.

The ID of the note that is linked to a time entry can also be retrieved using Xurrent’s Time Entries API. And when time entries are exported, the export file now contains the additional column ‘Note’. This column contains the ID of the note that was added to the assignment when the time entry was generated. This makes it possible for providers to pass the content of the related notes to their financial system for inclusion in the invoices they send out to their customers.

For requests, to which both public notes and internal notes can be added, it may be good to point out that it is the public note that gets linked to the time entry when both a public and an internal note were added when the time entry was generated. If only an internal was added, then it is the internal note that is related to the time entry.

A Note From the Road: What SPARK Taught Me About Time
During the second SPARK event in Antwerp, I stood at the back of a training room and watched a customer build a custom integration with our new iPaaS, wiring Xurrent to another system in her stack that had never talked to it before. No services rep doing it for her. No statement of work, no project plan with a kickoff and a go-live date. Just a person with live beta access in her hands, connecting two systems by hand, and finishing it before her coffee went cold. A year ago that would have been a multi-week project with a budget attached. She looked up, a little surprised it had actually worked, and said something I have not stopped thinking about since. She said it just gave her her week back.

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)














