Rollup Custom Field values from subtasks to parent task
K
Kathryn
From support ticket: Would like to have all number custom fields rollup within subtasks to the parent task
Log In
M
Margaret Lewis
Is there any traction on this?
Dani
Anthony C. Caroline Ginty any chance we can get this higher on the radar of the team please? It is crucial for all budgeting and forecasting usages of clickup and airtable/monday/Day after Sunday already do this.
We need it for numbers, $ and formula fields please.
Without it you have to only have one task in the group to use the calculation fields which is completely useless.
Note how the parent tasks do not equal the subtasks at all, they must be manually calculated. Allowing it to rollup gives you a subtotal so to speak.
In some rare instances I could see someone not wanting that functionality so a toggle inside of settings to not do that would be great but the default in my opinion should be to roll up just like time estimates do.
This feels semi related to the subtasks should inherit the parent task custom fields request as well. Both are creating insane amounts of manual labor and room for user errors.
Michelle Kreuter
Dani UP VOTE
J
John Wurl
Key differentiator between CU and Monday
M
Minh Bui
:D with this I can make the inventory management much much easier need it, :*
Caroline Ginty
C
Colin
I second that. It's frustrating me that I don't know where I am on overall prjects.
Rishab Patwari
Would really like to have all number custom fields rollup from subtasks to parent. This is critical for usage as a platform for budgeting and forecasting
Caroline Ginty
Merged in a post:
Task's informations are compilation of yours subtasks's informations
Lucas Modesto
- We understand that when a subtask is opened, the information from the original task should be the summary of the subtasks, calculated automatically (with the possibility of manual correction, in case of inconsistency). For example:
a. The duration of the task in days must be the ratio between the highest end date and the lowest start date (items ‘d’ and ‘c’ below);
b. The task start date must be the smallest date among its subtasks;
c. The task's end date must be the largest date among its subtasks;
d. The percentage (%) of completion must be the ratio between the sum of the amount of work performed on the subtasks and the total amount of work on the task.
Where:
Total amount of work = expected days;
Amount of work completed = expected days * quantity completed (%);
Percentage of completion = (∑ Amount of work completed) / Total amount of work
e. The percentage (%) completion field for subtasks that do not have subtasks or checklists should have the possibility of manual change, as there is no reference for automatic calculation;
f. The task status must be updated accordingly as the status of its subtasks changes:
Where:
Completed = If all subtasks completed;
Progress = If at least one task is in progress and none are stopped. Or if one or more tasks is not started among others completed, and none are stopped;
Stopped = If at least one task is stopped.
Caroline Ginty
A
Aga
I would suggest to add an option to choose if the value should roll up, or if the parent task shows the lowest or highest value of the subtask's values
Load More
→