LigaAI supports flexible automation scenarios to help eliminate repetitive operations and free up your team's productivity.
Automation is a feature that enables LigaAI automatically execute specified actions when triggers occur according to the rules you set up. Like assigning the work to someone when the status changes.
You can set a series of automation in a project and leave the tedious and repetitive affairs from LigaAI
Automation consists of Trigger, Conditions and Actions.
The trigger is the starting point of Automation.
Events such as work creation, field changes, Git commits, Jenkins build results, etc. can be set as triggers in LigaAI.
Conditions are an optional part of automation. Multiple conditions can be added to a trigger. The automation will only execute when the conditions are true.
Firstly, choose which objects the conditions control to make the automation more precise.
The work where the trigger occurs satisfied the conditions.
You can add fields, sprint or DevOps process conditions to the trigger.
Only if the subtasks of the work satisfied the conditions, the automation will run.
Select a condition type:
Subtasks Exist: The trigger work has subtasks.
Subtasks Do Not Exist: The trigger work has no subtask.
All subtasks satisfy conditions: Only if all the subtasks of the trigger work satisfy the conditions, the automation will run.
At least one subtask satisfies conditions: Only if at least one subtask of the trigger work satisfies the following conditions, the automation will run.
Only if the dependencies of the work satisfied the conditions, the automation will run.
Select a condition type:
Actions are what happens when Automation is triggered.
Automation can execute actions such as sending Webhooks, message notifications, work creation, and field modification. Multiple actions can be added to automation.
You can choose the objects that the actions execute on.