-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
1
-
Minor
Issue Summary
If you have a Custom Field related automation trigger with a card filter applied (i.e. "when custom field X is set on a card with the Y label), the {customfieldvaluebefore} variable won't populate the field's previous value.
Steps to Reproduce
- Create sample automation: "when custom field X is set on a card with the Y label, post comment "{customfieldvaluebefore} has changed to {customfieldvalue}"
- Trigger the automation
- Notice the comment is "has changed to [new value]", rather than "'[previous value] has changed to [new value]"
Expected Results
The comment should reflect the Custom Field's previous value and new value.
Actual Results
The comment only displays the new value.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available