Caroline Ginty Amazing! Excited to try it out!

Caroline Ginty I have already used it today for our workflows. It is super useful, as it eliminates the need to create an automation that would do the same thing. Thanks for listening to us guys

Caroline Ginty does this also work for forms?

Ruud It looks like this isn't working for Forms right now; I'll have the team pick that up since it's intended to work for Forms.

Caroline Ginty Awesome! Thank you!

Caroline Ginty

New subscriber to ClickUp and so far it seems as though it is a great tool, so congrats and thanks for all the effort. I wanted to confirm that this feature request will include functionality that will allow for default values at each level of the space-folder-list hierarchy. I ask because although automations can do this, default value is a pretty basic piece of functionality relative to what automations really ought to be used for. As one can imagine it wouldn't take long to reach the 10,000 automations cap if one is even just setting 2-3 default values for each task (let alone more) and has a ~10-person team active in the system. Thanks for your help.

Javier Benson Thanks for reaching out! Default values will be able to be set on the field level, so will apply to any/all locations where that field exists. For example, if Field A exists on List B and Folder C, the default value for Field A will be the default for tasks created in List B and in Folder C.

This is consistent with our other field-specific settings, like pinned and required, which also apply in all locations. Of course, different fields can be used in different locations with different default values if that is a better fit for your use case. Cheers!

Javier Benson agree with you that adding hierarchy levels to fields would improve efficiency and decrease the need for so many automations. I use the same fields across multiple spaces but not being able to customize whether they are pinned or required at a list view is limiting. However, it feels less complex and messy than having multiples of the same CF. And using different CFs for the same info in different spaces/folders/lists restricts the view options, which is more important and impactful than pinning/required fields. Always seem to be creating workarounds to make things actually work smoothly.

Natalie Williams thanks for highlighting your similar experience and feedback. Caroline Ginty thank you for pushing this default value feature request forward. I think it is a great start! Looking at it now and will revert back with any feedback.

Caroline Ginty This looks great, thank you.

Unless there is now a way to configure default values that I am missing, I would still greatly appreciate if the Click-Up product team could make note of those of us who need default values at a space-folder-list level (or at least at a space level). While I fully acknowledge Click-Up's need to promote automations for its business model (and using automations for complex logic makes perfect sense), I am sensitive to simple pieces of functionality (e.g. setting a default value in separate lists) that can result in geometric growth in automations. This makes it difficult to adopt the tool (in terms of cost, internal adoption, etc.)