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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


Butler: Optional wildcard field in pattern matching trigger

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.

1 answer

0 votes
Cody C_
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Feb 14, 2023

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:

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

Screen Shot 2023-02-14 at 4.36.28 PM.png

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events