Fixing certain Incidents, fulfilling certain Service Requests or carrying out certain Changes often require a fixed set of Tasks to be completed. While Task Management in Freshservice is great for breaking down work, it will be better with Automations.

Introducing Task-based Workflow Automations 

With Task-based Automations, Admins can configure rules

• To create process workflows through Tasks for resolving Tickets and Problems or completing Changes and Releases
  • For e.g. Task-based Automations can be used to create a sequential workflow of Tasks that need to be completed for fulfilling a new laptop request
• To route Tasks automatically based on configurable conditions
• To notify Users on changes to the status of Tasks
• To keep the parent Ticket/Problem/Change/Release fields updated based on Task events
• And much more!

Task-based Automations will be available for Ticket, Problem, Change and Release Tasks.

Hi Des,

It's still early days. We don't have an ETA yet. 

I'll keep this thread updated on the latest.

-

Sundar

Hello Leigh,

Yes, Task workflows can run in parallel with Ticket workflows. You're right that two workflows cannot be triggered for the same ticket at the same time, and similarly two workflows cannot be triggered for the same task at the same time. However, Ticket workflows and Task workflows can execute in parallel.

-

Sundar

Product @ Freshservice

Hi Tom,

Ability to set field values from placeholders dynamically is not something that will be available in the first cut of Task automations. We will eventually extend support for setting values dynamically in the action blocks, not just in Tasks, but across all Automators. For now, I'll add your request against that.

Thanks for your feedback.

-

Sundar

Product @ Freshservice

Hi Alex,

We are trying to get this feature prioritised for the immediate future. I don't have concrete release date yet. Kindly stay tuned.

-

Sundar