Field assignment on Child tickets created via automation rules after Parent ticket was created
We use one automation rule to create Child tickets (subtasks) when a parent ticket is created from another department ( example Onboarding/offboarding), and a second rule to assign a technician to each Child ticket.
The second rule never triggers, because Atera does not allow an action performed by one automation rule (creating a Child ticket) to act as a trigger for another rule. As a result, Child tickets are always empty and created without a technician assigned, requiring manual assignment every time.
Please consider:
* Allowing automation rules to trigger other automation rules, or
* Allowing technician or other fields assignment to be configured within the same rule that generates the Child tickets.
1
vote
Roberto Zampieri
shared this idea