Hemant Kumar

Thanks !

Could we chose where to place them ? Folders seems to always go on top of the list and this isn't always what is best (I cancel the subfolder then because I don't want it on top).

Also, could we subfolder sprints?

Great news, this one's huge for us. We run BHP copper operational readiness projects in ClickUp using a formal PMO structure: WBS, governed baselines, change requests, RAG roll-ups and earned value reporting.

Current setup: Space (project) › Folder (workstream, e.g. OR Scope Assessments SRE-DPS-ORSA) › List (package, e.g. SRE-DPS-ORSA-010 Marketing) › Tasks (deliverables, e.g. 1.0.1.001 Marketing Strategy). Our WBS goes 4-5 levels deep, so right now the lower levels end up in list names and task ID prefixes instead of the real hierarchy.

What we'd do with deeper nesting: Project › Phase › Workstream › Package › Sub-package, with each folder matching a WBS code.

What would make it work for us:

Roll-ups at every level: custom fields (Planned Value, Earned Value hours) and progress should total up through each folder level, so we can report SPI/EV at any WBS node.

Dashboards that include child folders: filtering a card by a parent folder should pick up everything beneath it, including native Line Chart S-curves in scheduled PDF exports.

Inheritance with overrides: statuses, custom fields and permissions cascade down but can be overridden at any level. Client guests should only see their own branch.

Safe moves: moving a folder shouldn't break custom field values, baselined dates, automations or dashboard filters.

Folder-tree templates: save a full nested WBS structure as a template to spin up new projects fast.

Breadcrumbs and codes: clear breadcrumbs in views and a way to show the full WBS path on tasks.

For us, 4-5 levels would cover it. Happy to walk through our setup if that helps.

Update: we've started building nested subfolders 🚀

Subfolders shipped earlier this year, but they only go one level deep, and a lot of you have told us that isn't enough for client, project and department setups. Eng work to support deeper nesting (Folder › Subfolder › Subfolder...) is now in progress.

We'll share more on timing and exact details on how many levels we support once we're further along. Keep the use cases coming in the comments, they're directly shaping how we build this.

Follow along here: https://clickup.canny.io/admin/feedback/feature-requests/p/nested-levels-of-subfolders

Hey everyone, quick update

Next up in line: Nested Subfolders (this is planned and part of our roadmap. In research/scoping phase right now)

Hey everyone 👋

Deeper subfolder nesting is one of the top requests and we've started scoping it out. Today you get one level of subfolders (depth 0). We want to know:

Quick primer on how we count depth:

📋 Subfolder Nesting Depth Survey

We'll keep this thread updated as we make progress. Thanks for pushing us! 🙏

Hey everyone, I have created a separate post for Nested SubFolders. https://clickup.canny.io/admin/feedback/feature-requests/p/nested-levels-of-subfolders?search=subfolder&sort=top

Please vote if you need nested SubFolders. Also feel free to respond in the post about how many levels will be sufficient for your usecase

Hemant Kumar, do you have a feature request link anywhere so i can vote?

Where can we vote for nested subfolders?

Excellent! Subfolders within folders help a lot with organization.

Hemant Kumar hopefully we're not waiting 7 years for nested subfolders.. ;) - Personally I'd rather you guys work on subtask permissions first or Bulk export all DOCS