I’ve been having similar problems with subtasks and sub-subtasks. I’m able to multihome (add a project) to a sub-subtask in my rule, but it doesn’t work consistently when the rule actually runs. The sub-subtask generates fine, but just doesn’t get added to that project.
I was told by support that my ability to multi-home a sub-subtask was the bug, which is crazy. Rules can generate sub-subtasks but for some reason it won’t be able to multi-home? I am still working through this with them but multi-homing subtasks has been very buggy (especially with sub-subtasks).
Ideally, you could each notify support about this thread, indicating 1) that you’re not alone, and 2) that I agree with @C_R_CT that it sounds fishy to suggest that you can’t multi-home a sub-subtask.
If you reach an unsatisfactory conclusion with Support, reply here and perhaps we can help escalate.
Just an update on my end. I reached the end of the road with support, and I was told I need to change my workflow. They said multi-homing sub-subtasks (via automation) is not supported, even though I am able to multi-home within the rule They suggested I use subtasks (vs. sub-subtasks) but that clogs up my view of the work that happening.
FWIW, the multi-homing feature of sub-subtasks via automation sometimes works. So I think my only path forward if I want to continue using sub-subtasks is to check if the rule correctly multi-homed my sub-subtask each time.
I’m certainly not satisfied with this result because the sub-subtask generates with variable information (due date, task description, assignee) per the rule, but mutli-homing seems to be the one that partially works.
@C_R_CT, if you have to limit subtask levels, and in case you hadn’t already considered, perhaps subtask sections could help you. They stay at the same level but establish a visual hierarchy and I’ve used them to good effect to eliminate an extra level of hierarchy:
Hi folks, I’m sorry to hear you’re running into issues with subtasks and rules. (Thanks for tagging us, @lpb!)
It looks like both issues are related to rules and subtasks, but have different root causes:
@Eva_Kučerová_EvKu, I see that your ticket is ongoing, and our Support team has confirmed that your case is related to a bug affecting certain rules involving multi-homing subtasks. A fix is on the way, so hopefully, once it’s implemented, your rules will run normally again!
@C_R_CT, unfortunately, your case appears to be tied to a temporary bug that allowed sub-subtasks to be added to projects via a rule, and this isn’t expected behavior. Currently, rules can only associate tasks and first-level subtasks with projects. I see the agent handling your case also checked with our Development team, who confirmed this is not a supported functionality.
I’ve reached out internally to see if they can provide any additional details on this unexpected behavior, and I’ll update you as soon as I hear back. Although there are no current plans to support associating sub-subtasks to projects via rules, our team can file this as a feature request for future consideration. I’m really sorry that we couldn’t offer a better workaround for your case.
Sub-subtasks can be generated via rules (including dynamic information like variable dates, custom fields, task descriptions, etc). From my understanding this is expected behavior, and I have been using this in my workflow for a while now.
The only feature that apparently isn’t supported is multi-homing, which really doesn’t make sense to me. If I am able to create and customize sub-subtasks in automation, why can’t I also multi-home it?
FWIW I still have my sub-subtasks multi-homed and most times they multi-home correctly, but not always.
Also observing rules not working/being actioned on subtasks to trigger routing the sub task to a specific section or triggering the creation of a new task- the behavior seemed inconsistent earlier today and now rules don’t appear to be getting applied to sub tasks at all. The inconsistent/ineffective rules are very concerning as it may mean multiple teams do not have visibility into work that should be assigned to them.
Regarding the ability to multihome sub sub tasks as a “bug”- unfortunately, we were not aware this was not intended and built some complex automation around a very large effort of work that takes place annually and will need to rebuild the workflow from a new approach
Hi @C_R_CT, sorry if my message confused you! Yes, I meant that sub-subtasks cannot be added to projects (multi-homed) via rules, but they can be created via rules indeed.
I believe the behavior is similar to inherited custom fields, which only apply automatically to first level subtasks due to the close connection. If the Developers have any additional information about this, I’ll be sure to share.
@Kathryn_Leigh, I’m sorry to hear that you are also having issues with rules. I’d recommend reaching out to our Support team so that they can look into the logs and confirm if it’s related to the bug they are currently fixing, or if there’s any other problem causing this inconsistency.
@Vanessa_N Sub-subtasks can inherit certain custom fields (date fields and text fields) so I don’t understand the logic here. My automation has successfully multi-homed sub-subtasks in the recent days so I’m hopeful the functionality can remain.
@Kathryn_Leigh I was able to multi-home sub-subtasks in my automation and recently it has been working as expected. Though there have been issues in the recent past with the sub-subtasks not multi-homing. I’m holding out hope that it will continue to work.
Quick update for those who were experiencing issues with subtasks not correctly appearing in all their assigned projects — this should now be fully resolved!
Thanks to the Engineering team for jumping on this so quickly. I’ve tested it on my end and can confirm that subtasks are now multi-homing as expected.
If you’re still seeing any odd behavior, feel free to chime in here.
@C_R_CT, I also got an update from the developers on sub-subtask behavior. They confirmed that the project field to multi-home sub-subtasks via rules is intentionally hidden because this isn’t a common or recommended use case. It adds complexity and can lead to workflow inconsistencies. However, this ability is not technically blocked, and this won’t change. Users can still enable the project field to multi-home sub-subtasks by clicking the sub-subtask’s description box and using the shortcut Tab+P, which will enable the project field.
That said, we believe the main issue was caused by the same bug that was intermittently preventing rules from correctly multi-homing subtasks, which also affected sub-subtasks. Since this has been fixed, your rules should now correctly multi-home subtasks and sub-subtasks.
I hope this makes sense! Let me know if you’re still running into any issues.
They suggested I use subtasks (vs. sub-subtasks) but that clogs up my view of the work that happening.
