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

How to access specific {customfieldvalue} to use as variable?

Igor Borges August 24, 2023

I have two automations:

1. when a card with custom field "a" set is added to the board, move the card to the top of list "{customfieldvalue}"
2. when custom field "a" is set, move the card to the top of list "{customfieldvalue}"

 

The number 2 works perfectly, but the 1 doesn't. Why?

Imagine that is because the buttle doesn't know what custom field I'm referring. If I can directly write that I want the {customfieldvalue} from "a" I think that would work.

2 answers

0 votes
Carolina Lopez
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 30, 2023

Hi Igor,

I wanted to correct my previous answer. The rule isn't working because the {customfieldvalue} variable is only available to use in rules that are triggered "when the custom field XYZ is set", such as the second automation you've shared.
Even though the Custom Field is mentioned as a filter in the trigger, the trigger still refers to a card and not to a custom field.

I'm sorry for giving you the wrong information before.
You can still use the {{%Field Name}} format as I mentioned in my first answer. In this case, your rule should be:

when a card with custom field "a" set is added to the board, move the card to the top of list "{{%a}}"

0 votes
Carolina Lopez
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 25, 2023

Hi Igor, welcome to the Atlassian Community!

Based on the triggers you mentioned, the first rule would only work when a card with the Custom Field already set is added to the board.
If you create a card and set the Custom Field, the rule will not be triggered because, at the moment the card was added, the Custom Field was empty. If you copy the same card, the new card created will already have the Custom Field set, triggering the rule.
The second rule runs perfectly because it's triggered when the Custom Field is set, so it doesn't depend on the card creation.

If the rule isn't working as I described in the situations above, please create a ticket with us here so we can investigate further.

In both situations, the Automation will know which Custom Field you're referring to because it was mentioned in the trigger. In case you want to refer to a Custom Field that wasn't mentioned, you can use this format: {{%Field Name}}
This article explains more about it: https://support.atlassian.com/trello/docs/working-with-custom-fields/

Igor Borges August 26, 2023

When I add the card to the board, it's already have custom field set, but it isn't working.

 

"Added" means created, copied, moved into the board or emailed into the board, right?

I'm moving that card to the board but it isn't triggering.

Carolina Lopez
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 28, 2023

You're right, "added" means created, copied, moved into the board or emailed into the board.
The rule should be working, the behavior you're seeing isn't the normal one.
I created a ticket on your behalf so we can discuss it further and report a bug if that's the case. You'll receive notifications about it by email, but please let me know if you don't receive them.

Igor Borges August 31, 2023

Thanks!!!!

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events