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!
T
Trent Rains
Beta user: Guest users are unable to see the custom fields by task type even though the view permission in the field settings is turned on.
Reed Holland
I'm really liking the feature but there seems to be a bug that in the mobile app, you see fields from all task types even if you are not using that task type in the list you are viewing. It seems like there needs to be a separation between task type custom fields and location custom fields on clickup mobile.
O
Ola
Raina Ahuja - We love using custom fields by task type — they’ve made our workspace far more organised and structured. What would take this even further is the ability to preset default task types separately for tasks and subtasks at the Space level, without relying on automations to change them.
In our setup, a Task represents a Client, and a Subtask represents a Client Activity. Right now, we use automations to convert subtask types, which works but adds unnecessary steps and maintenance. Having preset types available directly at the Space level would:
- Ensure consistent structure across teams and workspaces
- Eliminate automation dependencies
- Simplify reporting, filters, and views tied to task types
- Provide a more intuitive, scalable setup for client- or project-based operations
Having the ability to define default task types directly at the Space level (for both task and subtask tiers) would ensure every new item automatically follows the correct structure. This would make ClickUp even more powerful for teams that rely on structured hierarchies like projects → tasks, or clients → activities.
Robert Bush
How can we join the beta? Also is there an ETA on pre-release?
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?
Load More
→