When using the dropdown list for task dependency selection, tasks from all projects meeting the “type ahead” criteria are displayed. When the task name is too long to show the Project name in the selection box, it is impossible to identify the correct task.
Restricting the selection list to the current project would be helpful. Alternatively, expanding the hover function to include the Project name would help as well.
Note that the functionality works as desired in Templates
I don’t thing they would ever do that, Asana is all about breaking silos.
Definitely. My trick has been to go to the target task, copy the link, and come back to build the dependency by pasting the link instead of typing the task name.
You can’t be dependent on tasks outside of the template itself?
Hi @anon378679, thanks for providing this feedback!
I’ll keep you posted and let you know if we have any updates 
Thanks, Bastien … I apologize for not being clearer. I was asking that the ability to restrict the selection list to the current project be an option, not the exclusive default. Sorry!
I like the target task link suggestion … was not aware that could be done
As far as I can tell, template task dependencies are restricted to tasks in the template itself.
Thanks!
I tried to copy and paste the target task link into the dependency search bar and it does not work. I also would love to have the option to restrict the dependencies to the current project. I have several projects running simultaneously and they all have the same tasks. I need to be able to add dependencies for just that project and not accidentally add a dependency for an identical task in a separate project. Hoovering over the task dependency drop-down does not show me the project name. It’s really frustrating!
I just tested this and it’s working fine here. I would play with it some more as I’m 99% sure it’s OK. (Make sure you have access to the desired task from the project where you’re pasting.)
I think prioritizing the preceding tasks and then allowing you to select others would be helpful - currently, I am unable to select a dependency from my existing string of subtasks as it’s not appearing when I type out the name of the subtask (many subtasks are labeled the same) and it does not allow you to add the parent task name to narrow down the selection…
Develop a configuration option to limit the dependencies to only those tasks associated to the same project being worked on i.e. stop the reference to other projects tasks when adding the dependency. This is only required on some projects NOT all projects so cannot be a global setting. We’re having the situation where common task names are being used across multiple projects (as you’d expect) and the list to find the valid dependency is long making it hard and sometime impossible to select the right task from within the current project. I know you can add them in timeline view but because of the length of our projects, the drag n drop is not an easy task either. And I know you can paste a link in the dependency field but this is extremely time consuming on complex projects. Be great if the roadmap included an option for this in project settings.
Great idea, I’ll keep an eye on this.
This will be very helpful