ClickUp logo
ClickUp
Create
Roadmap
Feedback
Feature Requests
12634
Changelog
Category
Fields, Formulas, Statuses
Voters
Karl Hoffmann
I
IT_Liang Ku (古健良)
Hayleigh Radeck
C
Christopher Steele
D
Daniel Berdasau
Igor Canabarro
Martin Hiriart
C
Christina Vawter
Spencer Garner
Integration
and 4.6k more...
Powered by Canny
Let subtasks inherit standard/custom fields of parent tasks (copy field values from parent to subtask)
future
Nunatic
November 21, 2019
Log in to leave a comment
Log In
Nico Cactus
When you create a subtask that can inherit custom fields and especially in automations, you can choose to inherit parent tasks.
·
A day ago
·
·
Reply
Ana Paula de Souza Zimmermann
It would help the team a lot with this feature. Any predictions for when this might happen?
·
2 days ago
·
·
Reply
L
Lynn Spina
PLEASE get this option active ASAP - 90% of my subtasks run automations dependent on the Parent Tasks custom fields. I used to be able to run them, and some other update changed that. Conditional rules and retroactive applications would be helpful, but just standard copying of custom fields from parent task to it's subtasks is paramount for my functionality. Without it, I am manually copying about 25 custom fields into about 10 subtasks for EVERY parent task in order to run my automations. Please hurry!! And thank you.
·
6 days ago
·
Reply
Mariah Hird
Custom drop-downs and custom labels are important for inheritance in our workflow. Bulk apply would save a ton of time and bring our reports to a more correct status.
·
October 15, 2025
·
Reply
B
Briant Wells
This would be really helpful. is there an update?
·
October 10, 2025
·
Reply
s
sam hastings
What is the estimated release date of this feature?
·
October 9, 2025
·
Reply
J
Joey
Can we please get an update on this feature?
·
October 3, 2025
·
Reply
s
sandra shannon
Yes! Yes! Yes!
·
September 23, 2025
·
Reply
S
Shabharish
🚀
Exciting Update:
We’re actively building a Subtask Field Inheritance Automation app for the ClickUp Marketplace!
Many teams struggle with subtasks not inheriting field values from parent tasks, leading to manual work and inconsistent data. Our app aims to fix that with a simple, cost-effective, set-it-and-forget-it solution.
What We're Building:
  • Custom Field Inheritance (e.g., Client ID, Project Code) from parent to subtask
  • Standard Field Sync for Status, Priority, Due Date, Assignee, Tags
  • Simple Setup via a clean config dashboard (no Make/Zapier complexity)
  • Optionality Control to apply rules only where needed
💡
What We’d Love to Know from You:
  • Which Custom or Standard fields are most critical for inheritance in your workflow?
  • How valuable is a “pull” feature (e.g., parent inherits start/due dates from subtasks)?
  • Would Conditional Rules (e.g., IF-THEN logic) be essential for your team?
  • Would retroactive inheritance (bulk apply rules to existing tasks) save you time?
  • What else would make this app genuinely useful for your workflows? We’re all ears.
Your feedback will help us get it right. Thanks in advance! 🙌
·
September 22, 2025
·
Reply
R
Roman Grankin
Shabharish hello! I'm so glad you are working on it!
In our appliance repair business, each parent task includes custom fields like Client Name, Service Address, and Phone Number. These are critical for context. I need subtasks to automatically inherit these values so contractors working on subtasks can immediately see client details without manual entry. This would streamline communication and reduce errors.
·
September 22, 2025
·
Reply
S
Shabharish
Roman Grankin Thank you! This is super helpful for building the app.
In addition to having subtasks automatically inherit fields from their parent, do you think it would also be useful if updates to the parent task automatically synced to associated subtasks?
·
September 23, 2025
·
Reply
Joanna Tiger
Shabharish - Thank you! I am excited for this update.
For us, when a user submits a ClickUp form, those values are added to the parent task details. I want ALL of these fields to carry over to each subtask.
We use the values of these custom fields in the automated emails that ClickUp sends when specific subtasks are closed. If the custom fields for the subtasks are empty, the email will not be sent.
It is not user-friendly to copy and paste the parent task details into each subtask just so our automations work as expected.
·
September 29, 2025
·
Reply
N
Nirav Panchal
Shabharish
* Which Custom or Standard fields are most critical for inheritance in your workflow?
--> For us, we have created custom fields for Client Name, Task Frequency, Service Types, and Filling Year. All of these are custom fields and should automatically inherit from the parent task. An option to auto-inherit all custom fields from the parent task would work well for us. We should be able to manage this under List > Custom Fields > Edit > Toggle ON: Inherit from the parent task.
* How valuable is a “pull” feature (e.g., parent inherits start/due dates from subtasks)?
--> As of now, the auto-remapping of due dates is working fine for us. However, having the option to default the due date based on the parent task could be useful.
* Would Conditional Rules (e.g., IF-THEN logic) be essential for your team?
--> We haven't fully considered this yet because we've been relying on workarounds due to the feature being missing. I will share our specific needs with you in a week or two.
* Would retroactive inheritance (bulk apply rules to existing tasks) save you time?
--> Yes, this is critically needed. I have around 1,500 tasks where I am currently applying these inheritance rules manually to about 10 subtasks in each task.
* What else would make this app genuinely useful for your workflows? We’re all ears.
--> Bulk update of recurring dates is essential. All 1,500 of these tasks are set to monthly recurrence on a specific date. If I want to change the recurring date, I must currently go into all tasks and change it manually.
·
October 3, 2025
·
Reply
C
Chris Heysel
Nirav Panchal PULL!!!! In Agile, not being able to have your parent tasks simply adopt the unified, furthest, or last status of a subtask is VERY annoying.... would help a lot of teams.
·
October 7, 2025
·
Reply
N
Nirav Panchal
Chris Heysel Shabharish, I completely agree. Currently, we are manually setting up parent task status based on subtask. PULL would be really helpful. Adding to that we also have an automation in place if all subtasks are marked as complete, change parent task status to "To be invoiced".
·
October 7, 2025
·
Reply
Hannah Nurse
Shabharish - so glad you are working on this!!
Which Custom or Standard fields are most critical for inheritance in your workflow? Custom fields such as drop downs, free text, check boxes, email, labels, website and tags would be useful the pull through to subtasks a lot of these would be handy on the subtasks.
How valuable is a “pull” feature (e.g., parent inherits start/due dates from subtasks)? Yes it would be so handy, and to be able to select which fields can be pulled and not pulled would be awesome!
Would Conditional Rules (e.g., IF-THEN logic) be essential for your team? Having a think on this one, I actually cannot see a use case for us that this would apply to.
Would retroactive inheritance (bulk apply rules to existing tasks) save you time? YES! 100%
What else would make this app genuinely useful for your workflows? We’re all ears. To be able to see custom fields more easily in the task view mode, currently they are listed under the task but it might be cool if we could add these custom fields to the task description.
·
October 7, 2025
·
Reply
P
Petra Winter
Shabharish good to hear the feature is coming soon. For us, the link between the status should be mentioned as priority 1. This should be inherited, but should also change dynamically when the status of the main task changes. It would therefore be helpful to have the selection option for all fields: Inherit values to subtask Yes or No And if so, update dynamically with the main task or not.
·
October 10, 2025
·
·
Reply
Zoran Jablanovic
Shabharish, my answers to your questins:
we need possibility for all custom fields (selective) to inherit the values. Imagine creating a main task with 10 and more custom fields, then an automation that creates a bunch of subtasks that you each share with a different team (SOP). You would have to repeat the process for each subtask.
putting the values of custom fields. today you could collect them in the description but it doesn't meet the needs, since you lose the overview in a list view.
"pull” feature, I can't think of a case right now, but I guess can't hurt to have the option
Conditional rules are always essential
Thx
·
2 days ago
·
Reply
C
Christopher Steele
Shabharish this is excellent news! Can't wait for release!
I use custom fields to tag items based on sub-components of projects and other associations. Currently I have to set up automations or sometimes do this manually.
A pull feature would be great but i'd definitely like to have it as an option. Sometimes I use parent tasks as a container and grabbing dates all the time would mess up some of my views (I wouldn't want to see the container if I group/filter based on dates)
Conditional rules would be epic, I can think of a few ways I can use this to further organize my tasks.
Bulk apply would definitely help me for cleaning up either old stuff and helping others get in shape. VERY welcomed.
·
A day ago
·
Reply
Saad Mir
Came here to type this as a suggestion and someone asked for this in 2019?!?!?! 😨😨🤯�
·
September 20, 2025
·
Reply
Load More
→
Powered by Canny