Would really, really like to see this implemented.

Good morning. I would like to vote on the development of this feature request, considering that I don't understand it as a "feature request," but rather as a limitation of ClickUp. As it stands, that is, "the current limitation is that the Main Task can only view up to the immediate level and that the main subtasks do not have automatic tracking of the progress of the sub-subtasks," it makes it unfeasible to use ClickUp for project management and even OKR management. This is not a differentiating factor of the tool compared to competitors, and this directly impacts the final decision when selecting (or not selecting) ClickUp as a tool in my organization.

Is there any demand under development to address this limitation? It makes no sense at all!

Furthermore, the burnup and burndown charts generated by ClickUp are inconsistent and don't show the true information if the automatic progress of the levels below the main task isn't updated.

Any news on this? It's the main annoyance in our company now. Management wants an OKR view connected to our tasks with progress bars, but this makes it hard to achieve.

Will be moving back to Jira - based on this issue alone - Its impossible to tracl progression efficiently in clickup with out this

This is basic feature that hold a lot of things back on my work.

5 years in the pipeline. This should be fixed by now. This is a standard MS project feature.

I really like to track our company's OKR with the progress bar. However, not being able to break it down further without the automatic progress bar feature failing makes it worthless.

Visualizing the progress of the subtasks in the parent task is an extremely important resource in project management and already exists in any online management tool... I vote to prioritize!! I'm having to do a lot of automation and view to arrive at something that should be native, a lot of effort put into it.

This would be very helpful

It would be highly valuable if the Progress (Auto) Custom Field could include nested subtasks in its calculation. Many workflows rely on nested structures to manage complex projects, and excluding these subtasks makes the overall progress metric misleading