In multi-workspace setups, teams often separate high-level portfolio management (e.g., Projects and Releases) from detailed product backlogs (e.g., Epics, Features, and User Stories). Currently, when nesting tasks from one workspace as subtasks under a parent task in another workspace, the child tasks automatically inherit the parent's workflow (statuses). This forces teams to use the same workflow across workspaces or avoid proper nesting altogether.

We request the ability for nested tasks (subtasks) to retain their original workflow independently, even when the parent task belongs to a different workspace with a completely different workflow.

Proposed behavior:

Subtasks keep the workflow (statuses, status categories, automations tied to statuses) of their original task type and workspace.

No inheritance of the parent’s workflow unless explicitly enabled via a toggle (e.g., "Inherit parent workflow" option).

Other elements like custom fields can continue behaving as they do today (we are primarily requesting workflow independence).

Why this matters:

Current alternatives like task relationships (linked tasks) are not sufficient because:

They are not visually prominent in the UI (no clear hierarchy in List/Folder views).

Time tracked on related tasks does not roll up or display together, making it impossible to accurately calculate real effort and cost at the project/release level.

Dependencies and blockers are harder to manage and visualize without a true parent-child structure.

Key Benefits:

True hierarchical visibility: See an entire project with its Releases, Epics, Features, and Stories nested underneath in one view.

Accurate effort and cost tracking: Time entries from all nested levels roll up properly for realistic project costing.

Faster blocker resolution and progress monitoring across teams.

Maintain specialized workflows per team/workspace without compromising structure.

Reduced need for workarounds (duplicated tasks, manual linking, external reports).

Real-World Use Case:

Project Portfolio workspace: Contains "Project" and "Release" tasks with a simple workflow (Planned → In Progress → Testing → Done).

Product Backlog workspace: Contains Epics, Features, and User Stories with an agile workflow (To Do → Refinement → Ready → In Progress → Review → Testing → Done).

Teams want to nest Epics and Features as subtasks under Projects/Releases for clear portfolio oversight and cost tracking, while keeping the development team’s detailed agile workflow intact.

This enhancement would significantly improve ClickUp’s capability to support scaled agile and portfolio management in complex, multi-team organizations.

Thank you for considering this — it would be a game-changer for many enterprise and growing teams!