Custom fields by task type
building now
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
Hey Everyone 👋
I know there is a good number of people looking forward to custom fields by task type. I wanted to share this demo video I made for those in the beta, going over what custom fields by task type will bring.
Feel free to ask any questions!
If you signed up for the beta, we are working on some remaining items so we can further roll things out, but this is the team's focus!
S
Stephanie Zang
Raina Ahuja Converting fields from location based to task based does not work. Any timeline on that fix?
Josue Lony
I've noticed first that when you share a public link, with the Custom Fields shared, only location fields are shown on link, but task type fields doesnt show at all
Also, on mobile is just a mess, all the custom fields are shown in the task, doesnt matter the task type
Jon Rowand
We've encountered a severe limitation that Calculation Cards on dashboards were not updated to read Custom fields associated with task types. These dashboard cards were not included in this enhancement. ClickUp also prevents a field from being linked to both a Task Type and a Location, forcing a choice and we need certain fields to be tied to the Task Type.
I assume the fix would be either to create a second set of Calculation Cards that allow Custom Fields by Task Type or updating the original Calculation Cards to not block Custom Fields by task type.
Ivan Villa
Hey everyone!
A quick update: I'm excited to announce that Raina Ahuja will be taking the lead on this project going forward. She's fantastic and will continue pushing this feature with your valuable feedback. You'll probably see me popping into other feature requests as we ramp up new things for you all. 😀
Now that we have more people in the "Custom fields by task type beta," we want to make sure we're squashing any bugs you might find. If you run into any issues, please report them using the normal bug form, but be sure to mention that you're part of the "Custom fields by task type beta." This will help us route your reports and get things fixed as quickly as possible.
Thanks again for all your amazing feedback and for being a part of this beta 🙌
David Boon
Ivan Villa I was never able to get access to the beta despite signing up... i have a couple of orgs though associated with my account. Could that be why?
M
Mark Neroni
Ivan Villa The current version still displays all fields from the location (i.e., list, folder, space, workspace). We need a method that would allow us to suppress location based fields from being displayed for a given task type. It is important that the custom fields still exist at the location level. The task type should simply control which fields from the location to display for the given task. If I build a workflow using automations, I could then apply a different task type to show/hide fields applicable to that portion of the workflow.
Robert Hudman
Thanks for all your help Ivan
Raina Ahuja - would be great to catch up and provide feedback.
Scott Henning
David Boon Same, still no access despite signing up for Beta.
Liam
Hi Ivan Villa, I've noticed AI Agents aren't able to update custom fields associated with task types. Do you have somewhere I could raise a bug for you to look into, or is mentioning it here okay? Thanks.
Liam
Hi Ivan Villa / Raina Ahuja, I wanted to clarify for everyone reading this: I had actually disabled the visibility of the custom task type fields I created for Guests and Limited Members. It seems this caused the issue, as the AI agent executions were skipped due to lack of access to those fields.
kalachev.kirill
Hello!
Before reading, an important note: I submitted a request for demo access, but it hasn’t been granted yet. All the conclusions below are based only on the screenshots shared in this thread by other users.
I’d like to share our use case for custom fields and possibly ask for one more feature.
We turned “task types” into something like universal task categories (for example, we use: meeting, integration, project, contact, call, document, and so on) and we’re trying to apply them across our entire workspace.
But the problem is that it’s not enough for us to link custom fields either to task types or to a location. We need to link them simultaneously to both task types and locations. For example, a task with the type “document” in the CRM sheet may need its own set of fields, while in the Accounting sheet it may require a completely different set.
How will this be implemented in the first version? Will simultaneous selection of task types and locations be available at the feature release, or at least sometime later?
Ivan Villa
Hey everyone! Just wanted to say we have made another big push on getting beta users in. 🙌 We will be keeping an ear out for feedback next week after more people get to play with it and submit any quirks or pain points.
Now, if you aren’t seeing this in your workspace, we were having trouble with some of the IDs being invalid and some bounced emails. So, we have 2 options. Feel free to use the form again, but we are also looking to add a way to turn this on for yourself in the app. Working with the team on the details next week.
Josue Lony
Ivan Villa I've seen the new fields now and starting to make the changes to my space for a few hours now, it's amazing how is working, I will update my comment in a week, but right now this is a game changer
Thanks to you and to the team that made this possible
Francisco Rezende
Ivan Villa, I ended up not realizing the volume of comments, that there was a need to register on the form, but I need this functionality a lot, and this would help me a lot in many cases that I have on the same list, 2 types of task as different. I really wanted you to include me in this beta. I filled the form right now.
K
Kieran Thomas
Ivan Villa looks good so far; pleased with how migrating custom fields works. Have sent you an email with one query, but overall, looks promising so far! Thx to the team for all of their hard work
Rakesh Rathore
Ivan Villa when i wanted to move the existing custom field in the task type when specifically its file/attachment type field its freeze not moving, there are some bug with the file type of cusotm fields.
Ivan Villa
Rakesh Rathore Thanks for reporting! will get this in front of the team 💪
Josue Lony
Rakesh Rathore
Ivan Villa
indeed, thats what I was coming to report, all my "File type" custom fields just keep spinning and never migrate to the task type, I don't know if it has to do that is moving a lot of files or something like that.
I have to say that the files that I previously upload to those custom fields were around 25-300mb
Scott Henning
Ivan Villa How do we sign up to be included for Beta features?
Ivan Villa
Scott Henning Posted the link above. We will be doing another patch in the upcoming week. We will also soon make it so you can switch to using the beta early in the app, just need to work through the details :)
Ivan Villa
Josue Lony This is helpful we are taking a look at this one!
Josue Lony
Ivan Villa I have a workaround for these in the meantime, what I did its:
I create a test list where I created one task for each task type that I need to add the field to, then open the task and in the area where you will add new fields, just search for the one you need and it works
EDIT: Important, if the field doesnt show in the list its because its not at workspace level
S
Stephanie Zang
Ivan Villa I have attempted to convert existing fields but it just spins. I am working with just a text field, so nothing complex, but I have not been able to get anything to actually complete.
Liam
Ivan Villa amazing work.
Is it possible to liaise with Joey in order to tie compatibility together with the mobile UI?
Really enjoying the direction you guys are taking ClickUp.
Joey
Liam We have a task for mobile as well, but will be releasing a bit later! That being said, if you use Custom Fields by Task Type, mobile works ok and it doesn't have any major bugs!
Liam
I am pleased to hear this Joey wonderful news. It seems like a positive shift for custom fields in ClickUp on a general use level and also from the perspective of mobile when viewing a unit of work on the go.
This offers a degree of customisation that better aligns with the shape of the business using your platform.
W
Wout Verhoeven
Can I join the beta too?
Janne
Spotted this beta feature active in my workspace (though I haven’t seen an announcement yet). Looks very promising! A few bits of feedback while it’s fresh:
Field visibility in views:
When adding fields as columns, there's currently no way to distinguish between location-level and task-type (or item-type) fields—they all show up as workspace-level by default. As more fields get populated over time, this could become quite messy and confusing, especially in views where certain fields are irrelevant. A way to scope visibility by hierarchy (location, task type, etc.) would be extremely helpful.
Item-level fields in lists = 👍
I really appreciate that item-level fields can be added to lists and show as blank when not enabled for that task type. If these were only visible inside the item, this feature would be half as useful. That said, if your architecture allows, it’d be amazing if non-applicable field columns could be automatically hidden when grouping by task type. That would let me collapse multiple task types into a single list view without clutter from irrelevant field columns—huge win for simplification.
Load More
→