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

How to avoid Butler rule from executing on cards that are emailed in?

Edited

Hello, 

I currently have a Butler rule to do the following that saves us all a couple steps when we set up cards:

when a card is added to the board by anyone, add member @{username} to the card, and set custom field "Owner" to "{creatorfullname}"

But we are about to start using the email-to-card feature for requests that we receive through an internal form. Since there is no generic "board" or team email, we'll use mine; the result is that all the cards that get emailed in end up with me automatically added to the card and custom field.

Is there any way I can prevent my rule from executing on cards that are emailed in?

Thanks!

2 answers

1 accepted

1 vote
Answer accepted
Hannah Humbert - Simpla Workflows
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 17, 2022

Hi @Olivia Henao ! You could make your trigger conditional so it doesn't apply to all cards on the board. One idea is to create a list called "New Requests" and have all cards that come from email default to that list. For your trigger, it could say "when a card not in list "New Requests" is added to the board".

That's exactly the list we're using for the requests, so this is perfect, thank you! I didn't realize there was a "Not in" option for that trigger. :)

Well I've found a "solution" since posting, which is to roll "remove all members" and "clear [Owner]" into another Butler rule I made specifically for emailed cards. It works, but it's not exactly what I'd call efficient haha, so I'll just keep this open if anyone has alternate ideas. :)

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events