Different custom fields in subtasks
Juergen Hobrecker
We propose adding the ability to create subtasks with custom fields that differ from those of their parent tasks. This enhancement would significantly improve the flexibility and organization of data within ClickUp.
Benefits:
Enhanced Data Organization: Users could create complex hierarchical structures, such as project portfolios, projects, subprojects, and tasks, all represented as subtables.
Versatile Use Cases: This feature would support a variety of business scenarios, including project management, CRM systems, and financial management.
Efficient Data Processing: It would facilitate aggregations, roll-ups, and consolidations without the risk of duplication by utilizing 1:n relationships instead of M:n relationships.
Use Cases:
Project Management: Structure portfolios, projects, and tasks with specific fields tailored to each level.
CRM: Manage companies and contacts with relevant fields for each entity.
Financial Management: Organize invoices and invoice items with distinct attributes.
Implementation Suggestions:
Introduce an option to create subtask templates with customizable fields.
Develop an intuitive user interface for managing and displaying hierarchical data structures.
Implement features for easy aggregation and roll-up of data across different levels.
This enhancement would greatly increase ClickUp's functionality and versatility for various business needs, making it a more powerful tool for users across different industries.
I hope this request is helpful.
Log In
C
Cheyne Trammell
Yes. I came from Monday.com and this was a very nice feature.
Benjamin
Alex Nascimento
Juergen Hobrecker we need more people interested in this functionality. There's only the two of us. We have to campaign... Hahaha...
Ivan Villa
Merged in a post:
Customize Status and Disable Fields in the Parent Task that contain subtasks
Alex Nascimento
By adding subtasks, it could be possible to disable certain fields (such as custom fields) in the parent task, or to prefer a Status for the parent tasks, making it a header or reference point for the subtasks, without the risk of redundant or incorrect completion.
The parent task could have its own set of statuses (independent of the subtasks), allowing it to function as a general bookmark or indicator (example: “In progress”, “Finished”, “Waiting for Subtasks”), without inheriting the operational statuses of the subtasks.
Possibility to use formulas in the parent task that consolidate information from the subtasks (sum of values, percentages, etc.), improving project analysis and monitoring.
This will avoid Duplication and Inconsistencies: Redundant or misused fields would be eliminated.
Greater Clarity and Organization: The hierarchy between parent tasks and subtasks would be more evident and functional.
Flexibility in Management: Users could configure status and fields of the parent task independently, aligned with their work logic.
This functionality would make ClickUp more adaptable to complex projects that rely heavily on the relationship between parent tasks and subtasks.