Make standard fields/properties (due date, priority, etc) required when creating a task | Voters

Make standard fields/properties (due date, priority, etc) required when creating a task

Waleed Elaghil

October 3, 2020

Caroline Ginty

Merged in a post:

Allow making standard fields mandatory when creating a task

Eduardo Valdez

Response from Brain AI for this inquiry:
No, ClickUp does not currently allow you to make standard (built-in) fields—such as task name, description, due date, assignee, etc.—required for task creation in a specific List. The "required" setting is only available for Custom Fields, which you can configure to be mandatory when creating or updating a task.
If you need to enforce that certain information is always filled out, the best approach is to create Custom Fields for those data points and set them as required in your List, Folder, or Space.

February 11, 2026

Russell Saks

Any updates on this one, click up team?

Isabelle Drischler

Surprised that this hasn't already been implemented. It seems like it'd be an easy addition considering the feature exists in other areas?

Daniel Charles

It just seems silly that we have to create a "required" custom field for our start dates and due dates and then setup an automation to look for these fields and then populate the start and due date from there, when it would be much easier to just have a toggle to make these fields "required" on a space/list level by default

Janine Baker

I really need assignees required when creating a task. Is something that could be done?

Mostafa Hosni

Most needed

Sma Chu

+1 please por favor пожалуйста 請 s'il te plaît لو سمحت Bitte कृपया

Dmitry Dementiev

+1 Request. It's a must have feature for our processes.

Paul Newton

I'm so confused... 'custom emojis' is in the planning stages on ClickUp's roadmap... but required fields in task creation is not. I thought ClickUp was a project management tool...

Thyle Carroll

Setting "Resolution" flag when closing a task is a fundamental feature. So this is more about when moving a task to a status (ie. CLOSED), making fields mandatory, so that you can group these later. An anti-pattern is creating a separate Status named "Won't Do", when this is a resolution type for a closed or done issue.

→