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
B
Brandon Mol
On March 1, I received an email form Clickup indicating this was a new feature available, but its nowhere to be seen in the app.
D
Dinuka Liyanage
Brandon Mol its mentioned as coming soon here https://clickup.com/features/custom-task-types
B
Brandon Mol
Dinuka Liyanage thanks. The emailed version, as per my screenshot, didn't have
the little "coming soon" mark. I guess someone in marketing jumped the gun a bit.
Alexander McArthy
Do we have an ETA on this? We've been patiently waiting for years & nearly at our wit's end as it's hold up a lot of workflow improvements. There's really no practical use for 'Task Types' until features like this are implemented. For now it's just aesthetic/labeling. CU is my fav app (period!), I don't want to have to go anywhere else!
Caroline Ginty
Merged in a post:
Assign fields to task type
Jeremy Stoller
The fields needed on an individual task are most closely related to the type of task it is, not which space or list it is in. My Graphic Design tasks might need a custom fields for Graphic Dimensions, but I don't want that field showing up on other tasks in the space. It doesn't make sense to track the dimensions of, say, a Meeting task.
Ben Shorrock
This really will be a game changer! I created multiple task types today, so looking forward to be able to format the custom fields to reflect the information needed in them.
Do you have a rough ETA of when we can expect this? Is it a big build? Thanks again!
Caroline Ginty
A
Axely Congress
Agreed here. We actually started to migrate some of our clients to SmartSuite just to have different field types in the same folder that did not affect each other. I did not realize how much this is needed and until we were able to create an app that we could not create in clickup due to the custom field issue. While we love CU, we are forced to look for other solutions due to this one item not being addressed. I need my lists to be independent of one another in a folder, completely, and currently you cannot do that in CU. Hope they fix this before we have to completely abandon ship.
S
Stephanie Henry
1.) I assume this will change what fields you see when you open a task (and please correct me if I'm wrong).
2.) But what is the plan for how this will look from list view? When you have multiple task types with their own set of custom fields. Will there just be a blank box that still takes up space on the task types that do not have ABC Custom Field? I imagine this would lead to a ton of wasted space with blank boxes from list view.
Ivan Villa
Stephanie Henry:
- Correct thats the plan
- Something we are still figuring out, blank boxes is probably the simple solution but as you mentioned maybe would lead to more wasted space, but still hashing out the details.
pixojoy
Custom fields per task type? Big hype!
Ivan Villa
planned
Perry Wirth
Ivan Villa 🙏🙏😻😻
D
Daniel Urbano
Ivan Villa one question: adding a custom field to a task type would mean that it spreads to any location that task type is added to?
Example: a task type called "bug" 🪲should have a 'people' custom field for reporter and probably I want it to be in every single location I add the task type to.
But... I have another use case: we use drop-downs custom field by projects that can give me information for any particular project. And each location is a different project that needs a different drop-down custom field for that same BUG 🪲 task type.
Would that be possible? Is that being considered?
Ruark Ferreira
Ivan Villa AWESOME!
S
Stephanie Zang
Ivan Villa Amazing! Is there a timeline in which we can expect this feature?
Josue Lony
Ivan Villa It should be nice to get as well statuses by task type:
Ivan Villa
Daniel Urbano:
Your first example is correct. We want to make it simple to define an object once, and the fields always belong to that item.
The second use case sounds like it's more granular by location. We have looked into it, but we are being cautious right now not to overly complicate it. Ideally, we can get the simple version out first to help most use cases. Then, if we can figure out a good UX, we can see how we can build on it.
Ivan Villa
Josue Lony: Yes, this is on my list too! Statuses become a bit trickier with how we currently handle status cascading, but the team will look into that on our end.
In the meantime, we will push towards getting the fields in for everyone :)
Ivan Villa
Stephanie Zang: No exact date yet, but as we get out of planning phase and into development I will make sure to update the progress here.
A
Arun Kalavagunta
We may have to move out of clickup due to this limitation. What is the ETA?
A
Axely Congress
Arun KalavaguntaI We too are moving because of this limitation. It is a huge deal breaker now that we have found suites that truly allow for custom field independence.
A
Arun Kalavagunta
Axely Congress what are you moving to?
A
Axely Congress
Arun Kalavagunta: Moving to SmartSuite. The field management is exactly what we needed. They are missing a lot of the cool AI features of CU, however to be able to independently manage a table/list, with its own field is amazing! Every table is its own entity, meaning I can even have the same field lables for different tables and they do not cross. They are new to the scene but this one feature alone makes the jump for most of my clients worth it. Lists in CU should be independent, and if i delete a field in one list it should not affect all fields in different lists. Drives me crazy that I cannot have two lists with two independent fields named "Phone Number" for instance. Clickup is the bomb but a nuke has been dropped by SmartSuite.
Load More
→