Set Custom Fields at the task/subtask level | Voters

Set Custom Fields at the task/subtask level

Matthew Flex

I think it makes sense to have custom field enabled at the level of Project. However, it would be very useful to be able to select which custom field to display on a per task basis. Right now, my team has a dozen custom fields in on project but most tasks only need 1-2 of them. So there's a bit of visual clutter happening.

It seems I recall a little eyeball icon when I was in Task > Manage Custom Fields, that allowed one to hide/show select custom fields. I believe I use this on 10/5/18. Dev experiment perhaps?

October 6, 2018

Marius

6 years old request, 800 votes, not even on the roadmap. I often times struggle to understand how ClickUp prioritizes where their customers' money goes...

Louise Krångh

This is a must have for our business.  
We have  parent tasks that represent the customer. 
Under that we have subtasks representing the orders made by the customer and under that many subtasks containing specific order details. 
The custom fields used on each level is different. 
And we need an automation that makes an order-tasks status depending on a custom field checkbox, and that should not be visible on parent level

Luis

Bumping this up too. I use subtasks because they have due dates (instead of checklists). It would be great to have the ability to remove / hide custom fields within subtasks since the most parent task already has all the context / custom field values.

Ivan A

It’s need

Yuval Yacobi

BUMP Clickup Team.

Byron Gudiel

I really would like to have the option to remove a Custom Field without delete it in the entire environment, I will appreciate if you work on an update for this.

justinwj

What is needed is a Task Designer to thoroughly customize tasks

Alfredo Rivera

Please i really need this, is just the last piece to be the perfect choice

Raahul Dev

I also would like to have custom fields on demand. I would prefer having the option to create a custom field for a particular task or any other use apart from global availability. In other words, if someone wants a custom field to be available throughout the workspace, be it. If someone wants to create a custom field at a task level without getting populated globally, be it. Likewise, if someone wants to delete a global custom field when creating a task, this option is also available. This will bring great flexibility & reduce confusion for counting usages of custom fields.

Doriane Mouret

Also mentioned in a different comment, but ability to apply a custom field JUST to a subtask, not a task.

→