I have a project template that I am making that will apply to about 20 different product development projects. When I make a new dependency, Asana is automatically looking and giving me the names of the same tasks across all of my projects.
How do I make a single project self contained so that it does not try to make dependencies with other projects?
Welcome to the forum, @Derrik_Conrad! Are you talking specifically about limiting the available options for the dependency field? If so, I do not believe this is currently possible.
If you’re just setting up a project template, the way I currently accomplish this is to do all the setup in a project and then convert it to a template (instead of building from within the template). This allows you to set up dependencies from a Gantt (or timeline) view, which is a lot easier (just drag/drop the link between tasks).
Totally agree! 
I also choose the moment when to “Save as template” carefully to get the most out of the much easier to use project editor than template editor.
For dependencies, I go another step further and use the Gantt multi-select and Chain dependencies bottom toolbar option whenever appropriate:
Thanks,
Larry
@lpb I had no idea that feature existed…game changer for our team
I’m so glad! Rare to uncover something you don’t already know.
But I don’t hear much about this feature and I bet you have company.