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
Marge
Up! This will really be helpful to organize and reduce redundancy of having the same fields just because of the *required setting.
Brayden Ankerstein
This would be extremely helpful
Avraham Jay
This seems very basic to me. How can a field be required for every single board within an organisation? Some fields are extremely mandatory for some parts of an organisation's work-flow, and other fields are entirely irrelevant for other parts of an organisation's work-flow?
Caroline Ginty
Merged in a post:
Custom Field Required for JUST subtasks options
Tim DeMasters
Since we're limited to organizing by Client (Folders), Project (Lists), Project Level Tasks (Tasks), and actual "to-do tasks" (Sub-tasks), I need the ability to make custom fields required at the Sub task level. NOT the Task level. In my case, "Hard Due Date".
Caroline Ginty
Merged in a post:
'Always' Required fields toogle
Right now, required fields are required only when you "add a task", but then it is impossible to make it required.
Even if you create tasks in bulk, it only requires the field for one task, not all of them.
It would be great if we could have ALWAYS required field or just required initially.
I added some other comments in this canny post:
G
Gavin Todes
This is very much a needed feature. Pinning & visibility to guests should also be customizable at more granular levels.
Serhii Serhiienko
We are also having this problem with our workflow setup. We have created a custom field for all our workspace and it has to be added in each space. But it has to be a mandatory field only for selected spaces. For others, it has to be optional.
A
Alberto Alonso
Agree with this. Required custom fields shall be defined per list, and not for the custom field itself. Depending on the location some fields are needed or not.
Tim DeMasters
Currently, the only option is to set custom fields as required at the Task level, AND all subtasks.
pixojoy
Running into needing this often for my custom field defining the "task type." A granular feature like this would be handy.
Load More
→