Granular settings for Required Custom Fields
Brent Evans
Right now, all required custom fields are required in every location that the field exists. Selecting specific locations where the custom field is required instead of defaulting to all locations would be helpful [from a support ticket]
Log In
A
Amber Jones
I agree that this is important and it shouldn't just apply to custom fields but all fields that are self-entry. Different lists have different requirements. This seems so obvious, wonder why it hasn't been prioritized yet, because there are multiple variations of this same feature request spanning years.
Caroline Ginty
Merged in a post:
Allow Workspace Custom Fields to Be Required per Space and not Globally
T
Théo Cornier
Currently, when a Custom Field is created at the Workspace level and marked as Required, it becomes required everywhere.
However, different Spaces have different workflows. I need this field to be:
-Required in some Spaces
-Optional or completely hidden in others
At the moment, changing the field location risks deleting existing data, which is not safe.
Please allow Custom Fields to be required (or visible) per Space, without impacting data in other Spaces.
Guy Mannerings
Definitely would like this!
I would like a Custom Field to be required, apart from in certain locations.
Caroline Ginty
Merged in a post:
Require Custom Fields In Certain Views
Kea Allen
Would love if I could require a custom field ONLY if it is visible in that particular view/ based on certain situations.
Example: I have a list that represents the clients I am supporting and a bunch of department-specific custom fields. Since there are so many custom fields combined/ that's an overwhelming amount of info the the client, I created views that each department can use for the client. I want to require that, for example, someone HAS to fill out x custom field if it's in x view. However, it'll make that field required in y view, even if that team doesn't need to fill out the x custom field.
This would even be helpful if I could require a custom field IF it was a certain task type.
Caroline Ginty
Hi Kea Allen - thank you for this feedback! We're getting closer to this as we have an open beta ongoing for Custom Fields by Task Type - I would encourage you to sign up to check it out! https://feedback.clickup.com/feature-requests/p/custom-fields-by-task-type
A
Amber Jones
Caroline Ginty This isn't actually the feature change that this post is requesting, so not sure why it's been merged here.
Nick Jones
We have automations that move tasks from one list to another during different project phases. I have CF's that are required in Sales, but not required post sales. I don't mind the custom fields being present in every list and subtask, but since they remain as a required field in the subtask ever task now has an irrelevant required CF that is not able to be hidden or deprioritized.
C
Candace Lytell
Just adding on to this granular setting request for custom fields: have the same apply to Pinning so it is location specific.
Or perhaps a selection for Pin/Require functionality that user makes selection whether it applies only in current list or across the workplace
Mike DeGeus
In order to use ClickUp for workflows, this is critical.
Patrycjusz Rodzyński
Just the thing I need in my company. It would useful to manage where CF is required and where not. Possibility to add a color for required CF's could make a big step for UX.
Marge
Up! This will really be helpful to organize and reduce redundancy of having the same fields just because of the *required setting.
Load More
→