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!
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?
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?
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!
Michael
Raina Ahuja I can't think of them off the top of my head, but if i have time as i roll across them i'll post here.
But the basic point is simply that there are instances wherein we want a CF to be applied to a specific task type, or category of task types.... EXCEPT(!).... there's this one list or two that it would be nice to have that CF in.
Again, it's a pretty simple concept. No real need to "ClickUpThink" it. 😉
Oh, and by the by, when are we getting Button CF by task type?!
Jon Rowand
Raina Ahuja a major pain point is that the initial release of custom fields by task type stopped short in not updating Dashboard cards. In particular, Task List cards. It requires that custom field is linked to a location and does not respect those linked to task type. ClickUp's current state 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. In short, the dashboard cards should at least function like a list view where it shows the custom field value if the task/row is the associated task type, otherwise then giving the "This Custom Field is not enabled for this task type" warning prompt instead of blocking all task rows with the "You'll need to add this Custom Field to this task's location before you can use it."
Jon Rowand
Raina Ahuja , ah and one more. I know this is already on you all's radar, but I'll add voice to allowing formula custom fields to be linked with task types.
J
Jenny Bausola
Raina Ahuja We tested the function and are happy so far, it helped cleaning up unnecessary custom fields for different task types (in our case project types). We now ran into the problem where we have some custom fields also being used in different lists and spaces for example "client ID" - now they are separate from the other custom fields and we can't order them correctly. The problem could be solved if the custom fields could keep their location for other lists and also be included in task types.
Also it would help if within the custom field manager we could sort the custom fields within their different task types. Now it is all grouped together and makes it hard to keep an overview or put them in the right order.
Also if we could choose if we want the custom fields within a task type to be displayed separate from location custom fields or grouped together. That would help with unnecessary scrolling and searching.
Helen Gamage
Raina Ahuja - we are using this and the user case is very simple there are custom fields that on one list we may not want on the full list but just a task type (and this leads into you may want it associated with more than 1 different task type too) and there is other places in the workspace where we may use the same field (for re-use to not have more to manage or for reporting) that actually we want it on the whole list rather than the task type. The task type acting as a workspace level is a huge issue for our company as we are big we have 4 different workspaces and they are split and private but these task type ones will show for everyone. We do not allow workspace level CFs for this reason.
Daniel Urbano
Raina Ahuja I have a Use Case that needs Custom fields by task type and location:
We implement software like SAP or Oracle, and we use ClickUp for project management with each client, but not all of them implement the same modules or have the same scope. There are fields that I need by task type (always apply for SAP or Oracle), but some other depend on the scope of the project (within SAP/Oracle projects, some require 1 module, others require 4-5).
Another way to solve it would be with active/inactive values on custom fields by location (dropdown or label fields).
This is something we can discuss further if needed.
Tony Henderson
Jon Rowand can you try this again? I had the exact same issue yesterday but today it seems to be working ok?
Jon Rowand
Tony Henderson, thank you for letting us know! And, that is strange. I tried again earlier this morning and still getting the same blockage and warning "You'll need to add this Custom Field to this task's location before you can use it." I also tried recreating the Task list card on the dashboard to see if it would work now if I started from scratch, but that didn't work either. But, I checked again just now after a ClickUp reboot and it is displaying correctly now. I'll report back if it stops working again.
C
Camila Matias
If possible, expand the custom fields to allow multiple choices for the drop-down list and checkbox types
Yair Adi
I'm in the beta and testing very happy!
But i found on mobile it is showing the custom fields from others task type on top the traditional custom fields.
Also empty custom fields are showed between non-empty.
The expected behavior is to remain hidden until I touch "see all custom fields" exactly like on desktop.
Reed Holland
Yair Adi, agreed. I will be much happier with this feature once this is resolved.
Raina Ahuja
Reed Holland Yair Adi Thank you for the feedback - we're working on some improvements to the mobile display at the moment. Should be coming soon!
Michael
Yair Adi oh it's outrageously annoying.
Christine Marcus
Hi Team - I requested through the form to join the Beta group for this. Is it a closed beta? Or what is the normal turnaround time to know if you get to join Beta or not? I submitted the form over 5-7 days ago which is what was mentioned in the Form that's why I'm checking in this way. Thanks!
Raina Ahuja
Christine Marcus: Hi Christine! I just checked our list and you should've received access the week of Dec 15th. Let me know if you still don't see the feature enabled in your workspace and I can take another look to see what's going on.
Orejen (TH)
Hi ClickUp team, I submitted the form for this task type's custom fields and sub-folder feature 5 days ago, but don't see it applied yet. Could you please help me check my submission? And when I'm opted in, will I receive any email or notification confirming I have access to the feature?
Raina Ahuja
Orejen (TH): You should now have access from your workspace. Feel free to share any feedback here!
Orejen (TH)
Raina Ahuja Well received it, Raina. Thank you a lot.
Load More
→