Butler: Optional wildcard field in pattern matching trigger

[Ivan Li]

Is there a way to optionally match a wildcard field in butler?

For example, my trello card can contain comments of a certain format: "field1: value1, field2: value2" but it can also be empty: "field1: , field2: value2".

I want to pattern match the fields to populate customised fields and handle cases that it's empty.

[Cody Curry]

Hey Ivan! I'm not quite on the same page yet, but glad to investigate with you. When I'm working with automation, I find it's best to think in terms of a trigger plus an action.

In this case, what would you want to trigger your the automation? Would it be when a card is moved into a list perhaps? Or when a comment is added to the card? Next, what would you want the result to be when that trigger condition is met?

Here's an example of a pattern-matching rule you could use if you want to fill two different custom fields (named "custom1" and "custom2" respectively) when a comment is added with a specific pattern. The {*} represents a wildcard. The {wildcard1} is a variable that represents the value of the first wildcard in your trigger, and {wildcard2} represents the second wildcard.

We have more detail on pattern matching and wildcards here: https://support.atlassian.com/trello/docs/pattern-matching-and-wildcards/

Check it out and let us know if you run into any snags!