Although I love Project Templates 2.0, one feature I would love to see that would be a huge time-saver for me is the following use case:
- I have multiple types of Onboarding Project templates for particular types of positions
- I am responsible for the IT setup for each person onboarded, which is usually the same type of task(s) but given there are multiple onboarding templates, I have to manually go into each template and update the IT tasks to ensure consistency across all onboarding templates if I have to make a change
- Multiple project templates for each type of onboarding
- Task template for IT Setup that when I set it up, I can multi-home the task template in other templates (kind of like how you can multi-home regular tasks, but this function would be limited to task templates being able to be multi-homed between other project templates)
- Once a project was made from the template, the task template, turns into a regular task that only lives in that created project (unless you have specified that the task should be auto-multi-homed in another project) - this way you can avoid the action of completing the task it no longer appearing in any of the other templates it appears in.
This way, I don’t need to keep multiple tasks templates updated, but rather, just one task template updated system-wide.
I recognize this would necessitate moving task templates to be above the project-level in the system, but I argue this is better in the long-run anyway, just like Custom Fields are increasingly becoming more system-wide.