Blog
Insights & updates from our experts
.webp)
.webp)
.webp)
Blog
Dealing With Open Tasks Related to Closed Requests
Click To Explore
When a request is linked to a change, it is possible to close the request before all the tasks related to that change have been completed. In most cases, such requests should not be completed until all tasks of their related change have been finished. To prevent specialists from accidentally completing requests that still require some tasks to be completed, two improvements have been made.
The first improvement causes a warning to be displayed when a specialist changes the status of a request that is linked to an open change to ‘Completed’.
The second improvement makes it easier for organizations to look up completed requests that are linked to an open change. For this, a new filter called ‘Change status’ has been added to views and reports that are based on request data. The following screenshots show two examples of how this new filter can be used.
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.
5 Mins
September 10, 2026
Incident Management
Service Management
News
Enterprise
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
Service Management
Enterprise
Integrations