Hi,
I am trying to do integration between Clickup and Azure DevOps.
So I have 2 scenarios where when a new ticket is created, then create an entry on the other app.
Example - If a new ticket is created on Clickup, create it on DevOps.
Now, because there are 2 rules that create new tickets, duplicate tickets are getting created on the Initator app.
Example - Create a ticket on DevOps when a new ticket is created on Clickup.
Output—A ticket is created on DevOps, but it also creates a duplicate ticket on click up because another rule states that a new ticket must be created on DevOps. In this case, this is a new ticket for DevOps.
Please let me know how I can solve this duplication.
Thanks for your help.
Hi Indresh,
one option is to filter by the person creating the task. Is the person who created the ClickUp connection one of the people that can create tickets? If its not, then you can filter tasks by who created them and ignore the automatic ones.
Second option is to add a tag in ClickUp - “created by automation” for example and filter by that to prevent the duplicate trigger.
3 Likes
Thanks for your reply.
That is a good idea.
So when I update Devops from a new ticket on clickup, I am sending the clickup ID in a custom field.
So I want to use that as filter to not create ticket on Devops.
I want to say if DevopsID is Null then create record on Devops.
Can you please help me how do I set it up ?
Attaching my flow.
Thanks for your help.
Best Regards
Indresh Mishra
