Preventing duplicate card creation with Trello Automation

Rron Lamoja
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 6, 2023

I'm trying to create an automation rule in Trello using the Trello Automation. I want the rule to create a card on my QA board when a card is moved to the "Ready for Internal QA" list on my original board, but only if a card with the same name doesn't already exist in the entire QA board (regardless of the list it is in).

Unfortunately, I couldn't find a way to create such a conditional action using the current Trello Automation, as it appears to be more limited compared to the previous Butler implementation.

I've already used the "unique" parameter, but that only works for the specified list, it doesn't lookup the entire board unfortunately.

Can anyone help me find a solution or workaround for this issue? I'm looking for a way to prevent the creation of duplicate cards in the QA board using Trello Automation.

Thank you!

1 answer

1 vote
Vongsawat
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 7, 2023

Huh. Kept thinking of more and more convoluted workarounds that imperfectly addressed this problem. Then I learnt something new.

If you Find a card by name, and the only card that can be found is the current card, the automation ends early.

Basically an [If this card has a duplicate name, do the following] command

image.png

The second Find is to ensure it jumps to the just copied in card and archives that, instead of the older duplicate.

Jesi tinker-rein December 17, 2024

Would the copy card execute first and then it would always find a duplicate? 

Vongsawat
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 18, 2024

Automations always happen sequentially (though that can break down in certain complex niche cases you just have to trip over and exhaustively test to figure out..)

So the card gets copied first, and part of that command moves the Automation focus to the copied card.

Then it would search for a card with a duplicate name on the board and shift the Automation focus to it - or terminate the automation if it can't

If it did find the duplicate card, then it uses the second Find to switch the Automation focus back to the copied card. Then archives it.

Either way, you always want to exhaustively test out your automations (probably on a test board on a different workspace to preserve quota usage) to see if it works as planned etc.

Like Renato Fagaraz likes this

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events