Comment on page
With automations, you can configure workflow actions to occur automatically based on the conditions you set. Each automation consists of three inputs:
- The workstream where the automation is to occur;
- The trigger;
- The resulting action(s). You may choose to assign more than one action based on a trigger.
For example, in our Product Engineering workstream, when a task moves to our 'Ready for test' phase, we have an automation to set the assignee to
unassigned. In our workflow, this means development is complete and the task is now ready to be pulled by the next available person for testing.
As another example, you might choose to automatically move a task from one workstream to another when work is completed in the first workstream. For instance, when a tasks move to the 'Done' phase in a Design workstream, you might choose to have the task then move to an Engineering workstream. In these instances, the task is moved to the first To Do phase of the receiving workstream, unless a different work phase is specified by automation.
To see any automated actions applied to a task, click Task Activity from task detail:
While a workstream and trigger may be assigned multiple actions, we prevent duplicates of the same workstream + trigger combination.
We also check for any cascading effect across automations (i.e., action A leads to action B leads to action C…), and disallow in cases where the cascading would produce an infinite loop.
Last modified 18d ago