Avoiding Duplicate Notes
When a specialist sets the status of a request to ‘Completed’, the Note field becomes required. The same thing happens, for example, when the status is set to ‘Waiting for…’ in a problem or task.
But it happens fairly frequently that specialists add a note, save the record and then realize that they forgot to update the status. If the status was then updated to one that causes the Note field to become required, the specialist was forced to add another note, even though the previous note already provided the information that the specialist wanted to add.
This caused some frustration. To address this, Xurrent no longer makes the Note field required for a specialist if the same specialist added the previous note less than an hour ago. This should give specialists ample time to correct the status without having to enter another note.

This usability feature has been added for all record types that have a note field, i.e. requests, problems, releases, changes, change tasks, projects and project tasks.

Xurrent named a Market Leader in Research In Action’s Vendor Selection Matrix™ for IT & Enterprise Service Management Solutions
Xurrent earns #1 rankings in customer satisfaction, price vs value, and recommendation index in Research In Action's global ITSM/ESM Vendor Selection Matrix report.

Managing risks and delivering successful AI-driven outcomes at the Service Desk
Discover how IT leaders can navigate AI risks and achieve successful outcomes at the service desk. Learn strategies for cost control, robust security, and minimizing AI hallucinations to deliver measurable ROI. Download the Gartner report for deeper insights.
