Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How do I set a rule for when a specific custom field contains a text string?

Ben Miller April 29, 2025

I'm looking to create a rule for the following:

I have many cards coming in from Facebooks ads. I have a custom field which says Facebook for all of those, and I have another custom field which says the name of the ad campaign.


The ad campaign name always contains within it the name of the state. For example, CBO Leads Arizona MW18-65+ Interests Images. So I want to say that if that string contains "Arizona", move the card to a specific list. There may be many campaigns for each state, so I want to be able to create a rule based on a portion of the text string contained within that field, as opposed to a complete match on the field.

1 answer

0 votes
Brittany Joiner
Community Champion
April 29, 2025

@Ben Miller not sure if you're familiar with regex, but you can use regex in these automations, like this: 

 

CleanShot 2025-04-29 at 17.26.47.png

 

Just copy this and paste into the "set to" box: 

regex:/.*(Arizona).*/

(you can change Arizona to whatever and you can add multiple like this: 

regex:/.*(Arizona|arizona|Arkansas|arkansas).*/

 

Ben Miller April 30, 2025

Thanks! An Atlassian support member told me to use wildcards with this syntax: {*}Arizona{*} but it didn't work. Let me try your suggestion.

DiMaggio Tucci
Community Champion
April 30, 2025

@Ben Miller {*}Arizona{*} will require some text before and after "Arizona". The wildcards are referencing the text before and after.

 

Use the regex if it works for you. It should. That regex expression doesn't care if there is or isn't text before or after the string, so it's best.

 

Just as a reference, for example,  if "Arizona" is always at the start of the field, you would need to use

 

Arizona{*}

 

Just in case that helps anybody.

Like Brittany Joiner likes this
Ben Miller April 30, 2025

Thanks! There was text before and after Arizona, but it still wasn't working. Are we sure that wildcards (not regex) works on custom fields as well?

DiMaggio Tucci
Community Champion
April 30, 2025

@Ben Miller 

 

Are you willing to try another one? Just for the fun of testing it:

 

{?}Arizona{?}

DiMaggio Tucci
Community Champion
April 30, 2025

@Ben Miller 

 

That one previously and 

 

{?}Arizona{*}

Ben Miller April 30, 2025

For now I found another way to do it, but I appreciate all the responses!

Like DiMaggio Tucci likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events