Custom fields by task type
in progress
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
Sigurd Seteklev
in progress
Hey!
We are starting the work on this one. Looking forward to share the progress with you!
Benjamin
following! I would also like the ability to limit Custom Fields by subtask, similar to what is described here https://feedback.clickup.com/feature-requests/p/separate-custom-fields-for-subtasks
Sébastien Delvaux
Thanks for the test session. Question: How will these appear in the API? Ideally there would be no change to how they're nested in the API, and instead may have a new location/source parameter on each custom field present on a task so that we don't have to make changes to our external automations.
J
Josh Mullock
Please pick me!
Anthony Raad
We'd love your help testing designs for this feature! To start, we're opening up 8 unmoderated sessions (first come, first serve).
For this session, we’d like you to give feedback from a computer. It will take about 15 minutes to complete. In return, we'll send you a $20 Amazon gift card.
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.
**To get started, find somewhere quiet, then start the test here.**
If the sessions fill up, don't worry! There will be more opportunities for feedback soon.
Robert Hudman
Anthony Raad - Looks like I missed out on a slot.
This one is big for us, so happy to jump in when there are more times! 😀
J
Jamie Boeshart
Anthony Raad, this is a need for us, and we are happy to help where we can.
V
Vivek Prajapati
hey
S
Steve Hersker
Excellent news! This combined with "Task Types By Space or Private Task Types" would be a game changer for us!
I
Idy Weinberger
Amazing cant wait!
Elias
To make this really work we would need task typs per location (to not have an endless list of task types) and custom status per task typ.
Belle Niba
Sigurd Seteklev
1) Would you want to see task type and location based custom fields on tasks?
YES
2) Some use cases
SCENARIO 1 - Managing templates: We have a folder for managing templates. The folder has a list for internal and client focused templates. Each template requires a different set of fields. Unfortunately when we do save the template and load it in its actual location, it brings with it all the other custom fields that are not applicable. We do not have the option when saving the template to set what custom fields to exclude.
SCENARIO 2 - Relationships: When a task is moved from one list to another, the relationship field (even though it points to the same place) gets lost. For example, we do track prospects in Clickup. When a sale is made, the deal task is moved into our contracts location as well as to our revenue tracker. The deal task has a relationship field where we indicate the product, we also have a relationship field for the campaign that was used to close the client. However, we lose this data when the deal task is moved to another location.
Alex Benitez
Excellent!!! Thank you!!!
Load More
→