Description of the idea

Ability to generate subtasks directly from the form — e.g. one entry = one subtask within the main task.

For what

It allows you to turn the input data into an operational structure (task → subtasks).

Supports teamwork management at a detailed level (who, what, how much time).

Automates the breaking down of work into execution elements.

Why is it important

Eliminate manual rewriting of data for tasks → fewer errors.

Accelerate the workflow (input → execution).

Better control and transparency of work (each element as a separate subtask).

Critical for operational and production environments (e.g., brigades, multi-micro-task projects).

Please add this feature!!! The people yearn for subtasks.

The ability to create or even embed a form into sub-task would address a gap we have between our existing SDLC tool that allows us to create forms as a sub-task and ClickUp. Workarounds to this issue exist (i.e. create form and either manually link or make it a sub-task of work item) but, we've found them to be more labor intensive than just reverting back to and attaching a word document to the subtask.

Same - that would be super useful - it avoids having to create a dedicated list for example to collect bugs/feedback on an IT project for a customer

Any update here. This request was raised 4 years back!

I'm looking for the same but for purchase requisition. I want the requestor to fill out the general information once on a form which would be the task but then have the ability to create multiple line items (Subtask) for the items being requested.

Drift Boss - this is awesome

This would be amazing for me every single day! I have a client that needs multiple deliverables for different divisions under each individual project request.

This would be amazing....often you need information from a client, which then translates to work. It would be brilliant to have automation and conditional logic control what task/s were created!

I'd like to be able to create a form where the person filling it out can provide a list of things that need to be done that pertain to the main task (actual use case: a form to request a change order, and then the person would list all the things that need to change, and it would appear as ONE task with each change item listed as a subtask. (a checklist would also work but this request seems to have more votes).