Hi @Tracy_Hopewell1 , I moved this from English Forum > Product Feedback to English Forum > Ask the Community as it is more of a question than feedback to change Asana.
I think this is a bit much to dive into in the forum, but I’ll give you some high level pointers.
I don’t see that as an argument not to use templates. You don’t need to use relative dates.
That limitation persists with or without project templates. If you group the dependencies with tasks/milestones in between that could work as a workaround.
Main task/milestone blocked by Dependent group of tasks/milestones (up to 30) blocked by final dependent tasks (up to 30 per group)
Can you add some more context as to why you’d want this? If tasks are multi-homed it generally indicates that they are relevant for all the projects they are in. If that’s not the case the following procedure would be good to apply: Set “projects” visible in the list view to spot tasks that are multi-homed. (you can set this as a default view/tab in your template) Then when you remove or archive a project, use multi-select to “un-multi-home” the tasks.
General advice, don’t use automations in templates without using bundles. (Which requires at least Enterprise plan)
I have written some articles I think you might find valuable:
- Leveraging project templates - a deep dive
- As expected, everything went differently.
- Streamline work using Bundles
- ⚡ Pre-multi-home tasks in project templates
Hoping that helps.
JR