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 May 2026: Hi everyone - this feature is still on the backlog, but we will share updates here as they are available. Thanks!

Wim Delfs

Caroline Ginty Any news here? ... zzz

Wim Delfs

5.2k likes and it’s still on the backlog. How many likes does it take to actually get this developed?

Wim Delfs

Ciara O Brien

Chris Aitken

I'm genuinely surprised this hasn't been addressed, especially after years of consistent requests from your paying customers. Caroline Ginty, has your team spec'd or estimated this? Or is it sitting in a backlog abyss, unlikely to ever see the light of day?

Artem Kurganskiy

Oh wow, it's been 7 years since this was requested. I built this feature myself in an hour with a couple of simple API calls

Szymon Piech

Artem Kurganskiy, we're losing faith in the Clickup team's goodwill. Would you share how you set up the AIP calls so that someone from our implementation team can pick them up? We have paused ClickUp implementation for 18 months now, waiting for this feature...

J'Dian Bennett

Artem Kurganskiy, can you please help the group out and tell us what you did because ClickUp won't help us?

Denis Katz

Artem Kurganskiy I'm interested too

Artem Kurganskiy

Szymon Piech J'Dian Bennett Denis Katz Hi guys, so I built this externally in n8n (Make or Zapier work the same way, it is a simple flow).

Fire a webhook on task update. The payload's

history_items[0]

already tells you which field changed, the old and new value, and who changed it. Then send an empty "Update task" request: unlike "Get task", the response includes

parent

and

subtasks

. Branch on those two, pull the target's fields the same way, and only write if the target field is empty, otherwise you build an infinite loop.

Three things that are not obvious and will bite you:

Your own writes retrigger the webhook. Drop every event where
history_items[0].user.id
is your automation's own account, or you get execution storms that spill onto unrelated workflows.
People fields need
{"value":{"add":[ids],"rem":[ids]}}
, a scalar write silently does nothing.
"Parent has no such field" is not "parent's field is empty". Writing anyway returns a 400 and kills the run.

Jason Moseley

I can't understand by this still isn't prioritized. It's frustrating having to use other external tools to complete this functionality.

DANIELE RODRIGUES LIMA

This suggestion is from November 2019, has 5.2 thousand votes and is not yet on the implementation panel. That doesn't really make sense considering that other suggestions, with very few user signals, have already been implemented.
ClickUp, as a tool that seeks to stand out in the market, should have understood that user satisfaction is fundamental. In addition, when several people point out the need for an improvement, this represents only a sample of a much larger group of affected users.
This implementation is taking too long, especially considering the degree of importance it has.

EASE Co-op

Can this be moved up the priority list, ClickUp team? This is another standard feature in other project management tools that I would expect from ClickUp.

Veronica Brock

This would have a huge impact for our team. We need to view data across several custom fields. Most of those custom fields are set at the task level and we have had to build custom automations outside of ClickUp to set the values for subtasks via API. Even then, there are ways for individual subtasks to end up with incorrect or incomplete data in those fields. We would love to use more native ClickUp dashboards and visualizations for our data but we can't do that until we are able to set these values at the task level and trust that every subtask will inherit the proper values!

Kate Archdeacon

This would be a gamechanger for me - it's hard to consistently take advantage of the complexity offered by ClickUp when the task of assigning the complexity is manual. Please do make it a priority? As a solo PM, I'd preference this over further AI functions in the program.

Wim Delfs

Kate Archdeacon Couldn’t agree more. As useful as AI can be, it’s hard not to wonder why we keep getting more AI features while basic functionality like this (or PDF thumbnail previews) is still waiting on the backlog after years of requests.

Michael Ricardo

Hi! Any update on this?

In case it's helpful, i wrote out my org's use case:

Our org gives around 10 classes per week.

Each class has a duration of 10 weeks.

Parent task = 1 Class: for Example "English 1"
Subtask = 10 Sessions. (1 session for each week)

We've created dashboards to show us "today's sessions", this give us a task list of subtasks with a start day of today.

Here's where we can use the "inherit standard/custom fields of parent tasks.
each class has specific links, a student registration count, and several other descriptive fields that we have to manually copy every time we create a new parent task (which happens around 20 times a month)
If this feature existed, we would save a lot of manual work to copy over fields
and our dashboards will be a lot more useful!

Jenni Skarsten

It would be great if custom relationships could be included in this so that a viewer of the subtask doesn't have to follow the breadcrumbs to the parent task to be made aware that it is related to something else.

→