Set default value for custom fields on a per-List basis
Guy Mannerings
It would be great if we could set default Custom Field values on a per-List basis instead of globally.
Globally has been released (https://feedback.clickup.com/feature-requests/p/set-default-value-for-custom-fields), but per-List would be great!
Log In
Guy Mannerings
Caroline Ginty Any chance this could be looked at?
It would be great to be able to set a default value for a Custom Field on a per-List basis, as opposed to using Automations.
This feels like it should be baked in - so when you create a Task in a location, it already has certain custom fields values set based on that location.
Automations can be unreliable and slow sometimes, so they are not ideal. A native solution would be really great.
Caroline Ginty
Guy Mannerings It's not on our committed roadmap right now, but definitely something we'll continue to monitor!
Guy Mannerings
Caroline Ginty Thanks!
Adrienne Anghelone
Managing many clients means every List has unique needs. Setting default Custom Field values per List would save time, reduce errors, and keep tasks consistent—making workflows faster and more organized.
Mário Dominguez
This is very needed. Example: there's a field name 'Account' that holds the client to which this task is related. If there is also a List specifically devoted to that Client, tasks created there should have that field pre-populated with the default option.
I know automations can solve this but it requires to create rules for every single operation (create task, move task, edit field...).
Natalie Williams
Yes for this.