141
Automations - Allow custom field triggers to include changes from "Not Set" --> "Set" and "Any" --> "Blank"
planned
Guy Mannerings
Currently, there is no way to set an Automation based on a Custom Field changing from "Any" (or another field) to being blank.
This is really needed to get full use out of Custom Field-based Automations.
Log In
Zach - ClickUp
Merged in a post:
Automation Set Custom Field Value cannot set to empty
D
Dávid Burka
I am trying to set an automation to empty one of my Custom fields whenever the status of a task is changed. However, I cannot save the automation until I select an actual value for the field, thus I cannot empty it.
I assume this is not intended behavior.
Zach - ClickUp
Merged in a post:
When setting an Automation that changes "set custom field", you should be able to select empty
Guy Mannerings
Currently, if you set an Automation that changes a custom field value, you cannot set it to be no value.
What this means is you can't use automations to REMOVE values.
In this case, I want to have an Automation so that when the status changes to Done or Closed, a custom field label is removed so that it is blank (as this will mean it won't show up in lists I have that filter by that value).
This is not possible at the moment.
Zach - ClickUp
Merged in a post:
Allow automations for any custom field change w/o having to select the custom field
J
Jenna Kaufman
Allow an automation rule for any custom field change w/o having to select the custom field. That way I can create notifications when changes are made to criteria w/o having to select each individual criteria field.
Mariana Irazu
YESSS pleaseeeee
Maria K-B
agreed, it would be helpful to set an automation whenever a custom field is filled out by a dropdown that we created ! thank you
Zach - ClickUp
Merged in a post:
Custom Field Automation based on going from "not set" to "set"
Guy Mannerings
Can we get the option to run an automation when a Custom Field goes from "not set" to "set"?
This is currently not possible.
You can select "from: any", "to: any" as a workaround, but that comes with other issues, and includes actions you may not want to be included.
Zach - ClickUp
planned
Zach - ClickUp
Makes sense to me! Thanks for the callout
Guy Mannerings
Zach - ClickUp: Awesome! Thanks Zach. This will really help.
Jacob Green
We have a similar problem. I want to reset a target date field when the status changes and there seems to be no way to set a date field to blank through automation
Matthew Wester
Hi Dávid, thanks for leaving feedback on this current limitation! You are right, while Dropdown Custom Fields, etc., can be set back to having no value, there are other Custom Fields (like Text Custom Fields) where the Automation won't save unless at least one character is placed in the field. Would adding a single space into the Automation action field work for your workflow? You were right to post this here as a Canny Feature Request; this allows the Product team to keep this idea in mind for future improvements!
D
Dávid Burka
Matthew Wester: Hi Matthew, Thank you for your reply. Yes, we created an "empty" option the way you described. It works for now, but it is slightly inconvenient, that when selecting a value from the dropdown manually, two seemingly empty options appear at the top of the list.
Mike Lovato
Dávid Burka: I ran into the same issue today and think it would make sense to allow for a blank custom field in an automation. My use case: I've got some custom fields as part of a process that I want to be cleared when the task finishes moving through the process. I'll probably add an additional custom field dropdown option to accomodate it.
Load More
→