I have an automation that creates a ticket in XYZ project when a Task is moved from To-do --> In-progress in ABC project.
The problem here is the ABC project has global transitions (tickets can move back-and-fourth), in this case when the user moves the ticket back to To-Do and then to In-Progress, the automation is creating duplicates. How can I avoid this? Thanks!
You could leverage a label, component, or a hidden custom field that gets populated when the automation is triggered. Then, create a condition that verifies the label/component/custom field has not been set previously.