Blog
Insights & updates from our experts
.webp)
.webp)
.webp)
Blog
Add Automation Rules to Task Templates
Click To Explore
Automation rules can now be added directly to task templates. In the past, it was only possible to add automation rules to task templates that belong to a specific change or project template.
Being able to include automation rules in the link between a task template and a change or project template is still useful, because it allows different automation rules to be defined for a task template depending on which change or project template it is a part of. But in many cases, the automation rules for a task template need to be exactly the same regardless of the change or project template that it is linked to. So now automation rules can be related directly to a task template to ensure that these rules are applied no matter which change or project template was used to generate a new task based on the task template.
To add an automation rule to a change or project task template, open it in View mode and select the ‘Automation Rules…’ option from the Actions menu.
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