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 🙌
P
Pierre Masius
80% Task type, 20% Location I would say, even if I don't have a concrete example for second case.
Arnaud SEGUELA
Hello,
As far as we're concerned, we'd use 50/50 custom fields between location and task type.
Peter Yoder
90% task type, but can't really think of when i'd use the other 10% for location based.
Gurminder Dhami
Ivan Villa In addition to making Custom Fields "task type" based, one more thing that can be done is "Sectionize" the Custom Fields in "task view" (i.e. when a Task is Opened).
This will help in situations where a particular task has multiple custom fields that relate to different business functions and are headed by different teams (for example: Marketing, Operations and Billing.)
Having the ability to group custom fields in different Sections, would make it easy for the relevant team to just have a look at custom fields that matter to them and not to all the custom fields.
See, the attached images for better clarity.
![](https://canny.io/images/446f6f2060457733c16ff93ce87476ae.jpg)
Arash Masihpour
For me it's 100% Task Type and by choosing the default task type in a location, then it would be location based automatically. But limmiting Fields and Statuses to Location made many issues for me since 4 years ago starting to use ClickUp for all my works.
In my opinion, from ground zero, Status and Fields and everything that is related to Tasks (not it's location which only addresses them) must "only" be connected to Tasks and nothing else.
A
Adrian Taropa
Ivan Villa I think 100% would be task type based. The current setup makes sense if you just have one type which is task. But if I introduce another type which is say website, that website in itself will have different data associated with it than another content type person, regardless of what space those tasks are in.
What would be cool and I imagine somewhat possible with what you currently have is to allow me to select the available task types for each space. So for example I have a website build space, then the task types would be task and website.
If I have a CRM space, than the task types available to that space would be person. etc.
The current setup, by space, means that both person and website will have the same fields but empty, which may create some confusion and forces me to keep things simple to avoid having 50 fields per task of which only 5 may be relevant to its task type.
I hope this makes sense :D
T
Tom Rüther
If I had to choose then task type, but having the option to choose is always good, but makes it more complex.
If you need a field for a specific customer or team, it is easier to solve this via the location. Especially as in some cases fields are to be regarded as mandatory fields. And the distinction does not currently exist. In other words, the same field but different handling of the mandatory fields. I would do the ranking sequence like this:
- task type sets the standard
- location can overwrite task type. incl. the mandatory field specification
Kim Hoang (BF)
50% Task / 50 % Location
Judith Odor
80% task type, 20% location: a custom fields linked to the task type are more useful to me than location (if I had to pick one!), but I don't want to restrict the custom field from being used elsewhere also.
C
Charles Frey
70% TASK / 30% LOCATION
Load More
→