Blog
Insights & updates from our experts
.webp)
.webp)
.webp)
When requests are grouped together they are linked to a request group. This makes it easy for specialists, because they only need to update the request group. Any updates in the request group are automatically passed to the requests that are linked to the group.
So when a request group is completed, all the requests that are part of the group are also completed. At that point all the requesters receive a notification that encourages them to provide feedback.
In the past, when a requester pressed the thumbs-down icon in a grouped request and then used the Reopen button, the entire group would be reopened. Now, when a grouped requests is reopened by its requester, it is first ungrouped, after which its status is set back to ‘Assigned’.
This ensures that only the requester’s request is reopened, instead of the request group with all of its grouped requests.
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