Custom fields by task type
beta
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
Raina Ahuja
Hi everyone!
Thank you for all of your continued feedback on the beta so far and helping us shape the experience. If you're interested in joining the beta, please fill out the form here and we'll enable access for you shortly after - https://forms.clickup-stg.com/333/f/ad-3148517/2A0K2U2EQ5QDHYALUK
For those of your interested in custom fields on both locations and task type - we'd love to hear more about your use cases. Please share them in the thread below so we can understand your workflows better. Thank you!
Raina Ahuja
Hi everyone! Following up on my message from yesterday on Custom Fields for task types on locations (copied below) - we've added a few more slots if you're interested in participating and sharing your feedback!
--
Quick ask - we're adding Custom Fields for task types on locations, and we'd love your help testing designs!
For this session, we’d like you to give feedback on a computer. It will take about 15 minutes to complete and slots are limited. As you complete tasks and answer questions, the tool will record what you say and do. That’s why it’s important to speak clearly throughout.
In return for your feedback, we'll send you a $20 Amazon gift card. There will be more opportunities to provide feedback in the coming weeks, so stay tuned!
Here's how to get started:
First, find somewhere quiet and distraction-free. Then, start the test here or paste this link into your internet browser: https://app.usertesting.com/pp/85264d73-66b1-40cf-bbd1-9afd807e7b00
Daniel Urbano
Raina Ahuja Is there any way I can test it? No mind for the gift card for this test. I'm really interested on seeing this feature as a ClickUp partner.
Alexandre Lariviere
Hello, I have a quick question about requesting custom fields by type of task. Did you also think of putting the statues by type of stain or is it in another request? Also, if I request the beta version, what is the impact on my entire team? Does everyone have access to this version or only me? Thanks
Caiti Humble
This feature would improve Custom Field hygiene, but it does not address role-based assignment. In many workflows, tasks are already tagged with a role via a Custom Field, and the missing capability is to define a role-to-person mapping once at the project or folder level and have all matching tasks automatically inherit that assignee and stay in sync if it changes. Field scoping alone does not solve this assignment propagation problem.
A
Arabelle Lim
Hello. Please advise if you are going to enable the "Formula" and "button" custom field for the task type. Thank you.
Raina Ahuja
Thanks again for your continued feedback!
Quick ask - we're adding Custom Fields for task types on locations, and we'd love your help testing designs!
For this session, we’d like you to give feedback on a computer. It will take about 15 minutes to complete and slots are limited. As you complete tasks and answer questions, the tool will record what you say and do. That’s why it’s important to speak clearly throughout.
In return for your feedback, we'll send you a $20 Amazon gift card. There will be more opportunities to provide feedback in the coming weeks, so stay tuned!
Here's how to get started:
First, find somewhere quiet and distraction-free. Then, start the test here or paste this link into your internet browser: https://app.usertesting.com/pp/85264d73-66b1-40cf-bbd1-9afd807e7b00
TaeLynn Perez
Raina Ahuja I didn't get to this one in time, but if you decide to do another round of user feedback, I'm happy to help.
Raina Ahuja
TaeLynn Perez We added a few more slots today if you'd like to participate! Thank you!
S
Szymon Piech
Raina Ahuja Been testing those for few days, and all seems to be working as intended. It's a great help!
There are few things that would be great to follow... I think this should be relatively easy to achieve, but correct me if I'm wrong.
1) Custom fields in Project, Folder, List - those would apply and populate on all of the tasks within the relevant structure. i.e. if we have a folder, which is allocated to a client - we could have "Client name" set for this folder and then all the tasks would see the same client as it would be populated from the original folder. (if the task is linked to a different folder, the link would work with the original location, it would need to be moved for the value to change)
2) An extension to the logic - with the Task / Subtasks division - we could have a toggle where custom fields would only apply to highest level tasks, only subtasks, or both...
C
Crystal Dunn
Our org is a user group that would benefit from Task types per location/space and based on the location have certain custom fields due to the multi department usage. The simplest one is and most widely used type would be a Bug task. The information one department needs for a bug task is not the same information another may need. Also I would like to not muddy/add a bunch of irrelevent information to other spaces that may not need it. Product/Engineering uses 13 different task types which other departments may only have 2 i.e.
C
Chris Moore
Custom fields on task types would be great - one use case we have is for permanent and 'associate' resources. For associate roles we need to capture different data than that for permanent (day rate, inside / outside IR35 etc)
Jenni Skarsten
It would be an extra bonus if we could restrict custom fields to certain task types within a specific location
Raina Ahuja
Jenni Skarsten: Thanks Jenni! Do you see the need for fields to be reused more generally for locations (regardless of task type) AND used for task types within specific locations, or do you feel like the ability to restrict custom fields on task types within specific locations would support your use cases?
Jenni Skarsten
Raina Ahuja for my case I think the latter would be the most beneficial and the easiest to manage. Having it in both locations AND task types would be chaotic trying to locate what subsection it should be in within the custom fields section in the task view. Whereas, only appearing in the task type in certain designated locations would be more more valuable to me.
Natalie Williams
Raina Ahuja I'd like to see fields that can be used both for location regardless of task type, and for specific task types within specific locations.
Natalie Williams
Raina Ahuja adding on now that I've been implementing task CFs. They really need to be by task type AND location. Different teams had access to details in CFs because of the task types that they should not have had, so I've had to change back to CF by location to prevent data leaks.
Raina Ahuja
Natalie Williams: Thanks Natalie, appreciate the honest feedback here. We're currently exploring task type and location so this should support your use case better soon!
Konstantinos Tsiomos
We have been beta testing this feature and can confirm that it significantly advances several of our use cases. However, there is a minor quality-of-life issue that currently limits broader adoption.
When a Custom Field is set as a ‘Task Type’, it becomes available as a filter across the entire Workspace, effectively behaving as a Workspace-level field. While this is logically consistent, in large and very large Workspaces it results in excessively long dropdown lists and unnecessary scrolling.
A possible improvement would be to separate these categories into distinct sections (e.g. inside FILTER and GROUP) in order to keep the interface organized and render the feature better scalable.
Raina Ahuja
Konstantinos Tsiomos: I hear you! Would you need custom fields on task type (within locations) to also be reused for locations regardless of task type, or would it suffice to be able to control location for custom fields on task types?
Konstantinos Tsiomos
Raina Ahuja I would strongly prefer the second option: strict control of Custom Fields via Task Type, with explicit location scoping.
In my case, Custom Fields defined on a Task Type should remain exclusive to that Task Type and only be available in explicitly allowed locations. Reuse across task types via location is not required and would introduce both UI clutter and data exposure risks.
Let's assume an example with HR data. Imagine maintaining employee records as tasks. Certain fields, such as remaining leave days, may be visible to employees, while others, like internal performance evaluations, should remain strictly restricted.
If a task is added to another List or its Task Type changes, sensitive fields should not become visible simply because they are reusable at the location level.
From my perspective, predictability, data isolation, and security outweigh reuse. Location scoping should act as an additional constraint, not as a sharing mechanism.
However, I understand that the All Tasks view may face challenges around data accessibility. Since all fields can potentially be available there, it becomes critical to ensure that users cannot see data that does not meet the relevant Task Type and Location criteria. Without strict enforcement, this view could unintentionally expose sensitive fields.
I think that this model can scale better in large Workspaces and avoids turning Task Type fields into de facto Workspace-level fields in filters and grouping.
PS: Sorry for the long reply
Natalie Williams
Konstantinos Tsiomos totally agree with this: "Custom Fields defined on a Task Type should remain exclusive to that Task Type and only be available in explicitly allowed locations. Reuse across task types via location is not required and would introduce both UI clutter and data exposure risks." There needs to be control specifying the task type and location for every CF.
Load More
→