Let subtasks inherit standard/custom fields of parent tasks (copy field values from parent to subtask) | Voters

Let subtasks inherit standard/custom fields of parent tasks (copy field values from parent to subtask)

planned

Nunatic

November 21, 2019

Caroline Ginty

Pinned

Update Nov 2025: Hi everyone - this feature is one we are considering for next quarter's roadmap. It's still in pre-scoping stages, but we will share updates here as they are available. Thanks!

Alix Lepinay

I want this so much !

Bugra Oktay

marked this post as

planned

Koos Vis

Bugra Oktay great and thank you

Rob Kamphuis

Bugra Oktay You ripper!!

Guy Mannerings

Bugra Oktay Please make this optional. I definitely do NOT want custom fields automatically being applied to all subtasks. It should be asked as a question when you make a subtask, or set as a user setting.

Brynn Link

it would be great if tags were included in this - eg: subtask inherits the tags of the parent.

Joana Soares

When I move a parent task from Backlog to Sprint Backlog — that is, the user story — the subtasks remain in Backlog, and this has a huge impact on the reports I use to track the team’s workload points. The sum of the points from these subtasks in Backlog isn’t counted; only the points entered directly in the parent task are considered, which isn’t how we assign points. How is this not solved yet?

BALAORO, MIKE ANGELOU ROÑA

Please, this is very helpful for creating an automation and the action is send a channel message.

Frankie

Also raising my hand to say this is much needed.

Louise

Wow, this would really be a great improvement! Please, please, please start developing this!

Jairo Provenzano Ito

Stop everything and develop this! :)

Andrew Tomassetti

This is a big one. I have literally 40x the automations I need, because of duplicate automations specifically to create subtasks that carry a specific value based on another task with a specific value because there is no way to roll down field values. 
For example, we have a checkbox field for "Record a bug" so that when on a Build Task (think of it like  feature), we can easily record a bug, apply a template and task type, assign it and all that good stuff with automations. Its a single checkbox click to do it. However, we have many different systems we work on, and I need key information rolled down so that things like dashboards and lists that have filters show all relevant tasks and dont miss anything. This forced me to make 30-40 automations for recording a bug for different instances, all because there isn't a way to roll down fields. If the create a subtask automation allowed for inheriting fields, I could have 1-3 automations, instead of managing an entire library of duplicates. 
This feature is much overdue. Let's go ClickUp! :)

Ron Martel

6 years and almost 5k votes and your just considering it ?! This is the one thing I've wanted since I stated using ClickUp 5 years ago. I spend so much wasted time re-entering data that's already there. Please, Please, Please make this happen.

→