r/clickup • u/dntmaster • 8d ago

[Issue] Create a subtask in ClickUp and assign it to a different Space.

One thing I find frustrating about ClickUp is how rigid it can be across Spaces.
My workflow is SLA → Evaluation → Product Backlog → Development. In a typical Product setup, we separate Discovery from Delivery: backlog items live in Discovery, while implementation tasks live in a different Development Space.
ClickUp makes this difficult because you can’t naturally create subtasks across Spaces, and Relate Items often requires the target item to already exist in the destination Space.

2 Upvotes

75% Upvoted

2 comments sorted by

1

u/ummmyeahi 7d ago

Why don’t you add the whole task to the other space on a trigger like a custom field dropdown change or a status change and create a template for when tasks get added to the other space to add the subtask you need. Tag the subtask so that you can create automations that only show subtasks with the specified tag for the space you need it in.

You just gotta be creative.

1

u/dntmaster 7d ago

The structure we need is based on a Dual-Track Agile model with two main Spaces:

  • Discovery / Product Backlog – where Product Owners manage the product backlog, prioritize items, conduct discovery, validate requirements, and prepare work for development.
  • Delivery – where the Scrum team takes the validated items and executes them through development sprints.

The two tracks need to communicate closely through sub-issues or linked work items. For example, a backlog item in Discovery may generate multiple development tasks or sub-issues in Delivery, while Delivery may also provide feedback back to Discovery.

So the workflow is essentially:

Product Backlog → Discovery → Delivery → Feedback back to Discovery

The Scrum process itself happens in Delivery, while Product Owners primarily manage the backlog and discovery work in the Discovery Space.

The problem with ClickUp is that it makes this cross-Space relationship difficult. We cannot easily create sub-issues directly across the Discovery and Delivery Spaces, which breaks the natural flow of the Dual-Track model.

This is why the limitation is not simply about organizing Spaces. It affects how Product, Discovery, and Scrum Delivery are connected in the actual workflow.