I was wondering if there if it’s possible to create a rule that’d allow upon creating a subtask, the subtask will automatically inherit it’s parent task’s fields.
The use case is when there is a task created and there are multiple users assigned to different subtasks. For my org, each task also has a custom field for task types (technical, non-technical, project, etc) which is used when calculating metrics and efforts. Therefore for users tracking time and working out of subtasks, they’d need remember to manually select the fields within the subtasks, or risk not getting proper credit.
Therefore having a automatic way for subtasks to inherit the parent tasks’s fields will reduce repetitive work on users and not rely on users to remember to change the fields each time.
@Young_Pu we’re currently exploring a more native feature that would support this by default! Not sure of exact timeline for delivery, but it’s in design now
@Thaïssa_iDO To my knowledge you can’t trigger rules upon subtask creation, as they aren’t automatically part of the project. Or am I missing something?
I would also request in addition to this, a way to set task custom fields to automatically inherit changes to the project details. That way the same information could exist at the portfolio and project levels, but only need to be updated in one place.
I request enhanced subtask functionality to allow rules to inherit characteristics from parent tasks. Specifically, I want subtasks to automatically default to the same request type as their parent task (e.g., color/letter-coded sections like yellow ‘M’ for ‘More Info Needed’ or green ‘C’ for ‘Completed’) and for rules to apply logic based on parent task attributes — currently not supported. This would ensure subtasks reflect the context of their parent’s section, improving workflow consistency.
Hi @Daniel_Cohen-Vogel , do you want subtasks to inherit the parent’s field when you manually add the subtasks or when they are added via a rule?
If the latter, this can be achieved within the ‘Create subtasks’ action. Edit the subtask(s) using the pencil icon and look for the ‘+’ icon when you hover over your custom fields.
If the former, and you are on Enterprise, you can use the External rule action ‘Run script’ to use code to map the values to the triggered subtasks being created manually.
I’ve also merged your post into this existing one, which you can see is being considered
I understand. In our case, I’m trying to minimize clicks that users have to make, so asking them to manually change each subtask isn’t ideal. I’ll probably just remove the coding we’ve set up, so that rather than a task type of Request with letters displaying the section that each item falls under, we’ll just make all of the task types a Task with the same checkbox and no letters or color coding on each item. Not as visually appealing and a slight reduction in the user experience, but better than asking folks to make lots of additional clicks. Thanks for your help.
Supporting subtasks inheriting the parent project and relevant custom fields is in development now! Upon creation of all layers of subtasks, the subtask will inherit the parent project and all custom fields (the fields themselves vs field values). This will unlock other roadmap commits for the next two quarters which includes (but certainly not limited to) the ability to see all levels of subtasks within the list view (a full hierarchy tree view of parent and all levels of subtasks and their fields), support for display of subtasks on Calendar & Board views, Quick Find search / filter / sort / group by support for tasks and subtasks, and more coming.
I’m curious how this will affect rules triggered by “task added to this project” rules. Being able to set this rule to run on subtasks but then have nothing happen sure confused me at first.
Some questions:
Will rules with that setting start to trigger after the change?
What about when deselecting the option to run on subtasks?
Will subtasks become visible at the project level as well as the subtask level like currently after adding them to the project?
If not, what happens to subtasks that are already added to the parent tasks project?
@Jan-Rienk it’s like you’re reading off my UXR discussion guide for customers willing to talk to me about out subtask roadmap . I’m going to add this to our upcoming call to discuss
. I’m going to add this to our upcoming call to discuss