Custom fields by task type
planned
Ivan Villa
Problem:
Custom fields can become messy when you have different types of work (tasks) within the same lists. For example, having a bug, feature, and an epic task all in the same list would cause them all to have the same custom fields, even though I would want specific ones for each type.
Other issues arise when fields that should only belong to the top-level task spread down to all its subtasks.
Ask:
Custom fields should have the option to be added to a custom task type itself.
- Whenever I create a new task of that type, it will come along with all its custom fields.
- Those fields will not spread to any task that is not of that type.
Log In
Ivan Villa
Quick Poll:
If you could start over, what percentage of your custom fields would be "location" based (how it works now) and what percentage would be "task type" based? (e.g., 40% Location, 60% Task Type)If you have examples of why you still need both, that would be awesome too! Thanks in advance, this helps us make sure we build the right things for you all 🙌
S
Stefano Iavarone
To add to this:
Currently, filtering subtasks & exporting the subtasks ONLY based on parent+subtask filtering logic (ex: this custom field = this value in the parent & this custom field = this value in the subtask) in one row is not possible. So sometimes, we have to duplicate custom field values from the parent to the subtasks to make it easy to export and understand the data.
When implementing this feature request, it would help a LOT if:
A) We have the option to make custom fields visible in the subtasks, but read-only, ideally via grouping as per https://clickup.canny.io/feature-requests/p/organizing-custom-fields-into-groups-and-custom-fields-visibility-at-task-level. This should be a choice per custom field / custom field group with a default option, not global for the list/folder/space/workspace.
B) We have the option that when exporting a subtask, it also exports the parent custom fields in the same row in the CSV (even if they're labeled Parent: [Field Name] for easily distinguishing fields in the export).
K
Kyora Veira
Is there any update on this feature? Juleanne May Roque and Ivan Villa
K
Kyora Veira
100% based on task type
Antonio Eduardo
100% Task Type based Custom Fields.
I agree with @cielo that this is far more important than the "ai magic" stuff for us. This limitation is causing all sorts of confusion on our team, we had spent an insane amount of time trying to figure this out using lists. Which can get messy very very quickly.
Is there ANY estimative for WHEN this will be prioritized?
cielo
I wrote a whole thing but as usual, ClickUp's feedback page is super buggy and lost everything I wrote, here we go again:
To make ClickUp team understand how important this feature is, imagine this feature a task that ALL other tasks are blocked by, they ALL depend on this task. Now, be sure this specific task is this specific suggestion, got it?
We've put EVERYTHING on hold waiting for this feature, which is not even "progressing", we're literally paying charity now for ClickUp waiting for this, because once it is launched, we need to change EVERYTHING based on it, and all our plans will completely depend on this.
By completely, I mean 100%, and it is not us only, check out all the other comment, didn't see one single comment that need CF based on Location more than Task Type, all of them need CF by Task Type 50%-100% of their needs, and ClickUp is freezing the operations of all of these companies because they're focusing on useless AI "Magical" writing or some useless features. They're not bothering to even respond to this thread anymore!
Jeremy Stoller
Without this feature and statuses by task type, the whole task type concept is broken.
L
Lucas Medeiros
Ivan Villa any update on the ETA of this?
Karel VGH
Any update on this? Huge impact on Way of Working as of now :-)
Many thanks in advance!
J
Jorge Herrera
10% location, 90% task type
Dimitar Dimitrov
Zero percent Location and 100% Task Type
Load More
→