I’m wondering if there’s a way to have sub-tasks under a task template be true sub-task templates, in that if they’re assigned within the template, I don’t want them to show up on a user’s project list (since it’s a template).
I have Task Template #1, with two sub-tasks under it. For the parent task, I have that set to a specific assignee, and the parent task doesn’t show up on that user’s list until I actually create an active task from the template. However, for the sub-tasks under the template task, I have those assigned as well, but they do show up on a user’s list.
I want to be able to have the task template use the assignee field so that when I create a task and its affiliated sub-tasks from a template, the assignee is already filled in for all (parent task and any sub-tasks). But I don’t want it to show up on the assignee/user’s list until a task has been created from the template.
I don’t recall posting there, so may have been someone else?
And yes, that’s what I’m asking about. I’d like both the parent task and sub-tasks in a template to be assigned already so that when I create a new active task and related sub-tasks from the template, all of them are already assigned. But I don’t want any of them to show up as assigned to a user until a new, active task is created from the template.
When I create a task and sub-tasks and convert the task to a template, with all assigned to a user, the parent task of the template doesn’t appear as an active task on the user’s project list but the sub-tasks do. So that’s what I’m wondering about, if there’s a workaround or a specific way I need to do it in order to achieve what I’m looking for.
Screenshots illustrate what I’m talking about. Using myself as the assigned user for the test, the sub-tasks underneath the task template appear on my working, active project list even though they’re part of a template.
Thank you! I’m still seeing the same issue when I test creating a task template again, so I’m not sure if I’m doing something incorrectly. Can you reference the screenshots and explanation I shared with @Bastien_Siebman below and let me know if you have any other ideas?