Field inheritance between parent and child items. Custom Fields - automatically set to child items if parent gets value
Vidas
Merged in a post:
parent-child (custom) field inheritance
m
michael de decker
Hi,
It would be a convenient feature to have the ability to configure a (custom) field to allow it to inherit information from the closest parent item with data in the same column.
Example:
we create a custom field for Project ID's. If we configure the field to allow it to inherit from the parent, it would look for the closest parent item that has any information in said field and use that instead.
This would prevent the need from assigning the same project ID/... in every subtask.
Thank you!
Kr
Vidas
Merged in a post:
Tag and colour inheritance for child items and synched copies
W
Wim Verloop
I divide my workspaces in a what and a when part. So when I start working on something I make a synced copy of it to the when part (weekplan for instance). Is it possible to get an option to automagically inherit the tags and the colour?
That's what you get with the background colours in the statuses... Suddenly a plain white card looks... yuck!
Thanks!
Vidas
Merged in a post:
Child Items inherit tags and colour of parent item
W
Wim Verloop
I am not sure if in my earlier request this particular thing became clear...??? Could be a Workspace or Board setting, I do not really mind. But preferably a Workspace setting.
Vidas
Wim Verloop if I understand you correctly, tags and colors can be already synced. Teamhood allows configuring which item fields to sync via Workspace settings -> Item Fields menu. See the image. This functionality is available to all Ultimate and Enterprise plan subscribers.
W
Wim Verloop
Vidas After the upgrade it worked just fine, thanks!
W
Wim Verloop
Is the functionality to let this work for child items somewhere on the roadmap? It works for synced copies, but not for child items if I'm not mistaken...
Vidas
Wim Verloop: synced copies right now support primitive properties (status, progress, schedule, estimation, etc.). Item hierarchy, attachments and comments not yet supported.
We do not have it planned for this year (not much left anyway). But it's in the pipeline for Q1/Q2 (hard to tell exact date)
m
michael de decker
Vidas thanks for the info Vidas, glad to see it's in the pipeline! It would be great if we could be informed once there is a more concrete plan since this would benefit implementation a lot! :)
Vidas
michael de decker: hey, I've merged couple of additional posts in here and be aware that last comment on the pipeline is about Sync copy properties. It is not directly related to parent-child field inheritance. Parent-child field inheritance is not yet in the pipeline. But I am merging more requests which are about same concept, to align on user demand - the more the better - the faster it gets into pipeline. I am sorry if this got you confused.
Vidas
Merged in a post:
Sub-Task Custom Field inherit from Parent Task
W
Wallace Tai
If I create a parent task, I would love all the sub-tasks I create inherits the custom field value from the parent task, then I can modify the field I need instead of input the value of every custom field from scratch.
P
Petr Bár
Maybe you would integrate Yes/No box for copy of data directly to the Custom field creator. Or something like that to each child as a property for user´s current decision.
Vidas
Petr Bár: very valid idea!
Vidas
Petr Bár I see the value from it, the only thing we need to figure out is how to make it configurable, because I know quite a few cases where other users would want the opposite - keep parent/child values separated.