Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,459,508
Community Members
 
Community Events
176
Community Groups

Is the trigger "when the description of a card in list" broken?

Hi, I've created a few triggers that are intended to be specific to a given list, but they trigger for the entire board. Does anyone else have this issue? I'm not sure how to report a bug correctly...

Thanks!

matt

Example:

Complete is a list, Requester: is a pattern in the card description, Checklist is a checklist.

when the description of a card in list "Complete" contains "Requester: \n{* }", add an empty checklist named "Checklist" to the card, add item "Requester Agrees Complete" to checklist "Checklist", assign the item to member @{wildcard1}, set the item due now, and post comment "@{wildcard1} This card is finished. Please review and either raise an issue or check the \"Requester Agrees Complete\" check box. Thanks!"

2 answers

1 accepted

1 vote
Answer accepted

It is a bug, they will fix it eventually:

"

I heard back from my colleague, and this is indeed a bug. I'm afraid I don't have an ETA on when a fix for the issue will be pushed, as soon as one is available, we will deploy it.

In the interim, perhaps it would be useful to try a similar rule scheme using labels instead? For example, instead of triggering the actions based on residing in a specific list with a specific description, you could trigger those rules by adding a specific label. Not quite ideal, as it adds an extra step, but it would offer a fully manual way to trigger those rules in the interim.

"

Artemis Rising Star Apr 01, 2022

Hey @Matt Fisher, thanks for sharing the workaround that support provided! That will be helpful for others having the same issue.  

Like Matt Fisher likes this
0 votes
Artemis Rising Star Mar 28, 2022

Hi @Matt Fisher, assigning a specific list to your Butler rule should only trigger on cards in that list. The automation shouldn't trigger from other cards on the board outside of that list. Can you double-check that there aren't other similar rules enabled on the board that are causing the unwanted automations?

If you've ruled that out, you can reach the Trello team directly at http://www.trello.com/contact — use the "Using Trello" and "Report a bug" option to send an email to support who can troubleshoot this through with you.

Thanks for the reply @Artemis !

I did verify and submit a bug.

Like Artemis likes this
Artemis Rising Star Mar 29, 2022

Great! Hopefully a team member can help untangle this. :) 

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events