Blog

Options for Problem and Release Management

November 16, 2023

Patrick Bakker

1 Min Read

Click To Explore

In the Xurrent Development Update of two weeks ago, Xurrent Case Management was announced. By enabling one single option in the Account Settings, an account owner can simplify the use of Xurrent by removing fields and settings that may not be relevant to users of that account. Two new options have now been introduced with a similar goal. With these, the possibilities of Xurrent can be further constrained to exclude Problem Management and Release Management.

When the Problem management setting is disabled, the ‘Problems’ section is hidden from the Records console, the Problem Manager role can not be given to specialists, requests cannot be related to problems, and the reports related to problems are not visible in the Analytics console.

When the Release management setting is disabled, the ‘Releases’ section is hidden from the Records console, the Release Manager role can not be given to specialists, workflows cannot be related to releases, and the reports related to releases are not visible in the Analytics console.

The Account Settings page has been updated, bringing these similar settings together. A Field Help page has also been added, so that some of the lengthy explanations and explanatory links could be removed from the settings page, too.

Partners

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.

3 Mins

July 1, 2026

Service Management

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.

8 Mins

May 30, 2026