I am a project manager for a company that launches several products a year in multiple markets. I often use the same task name for different markets under separate projects. When setting up dependencies on sub-tasks, I am having a hard time distinguishing which one is the correct one to select.
Here is a scenario on the problem I am facing:
- Production is dependent on the Purchase Order
- Both sub-tasks have separate parent tasks
- In list view for Task: Purchase Order, I click on "Add dependency" and under "NEXT TASKS" I start typing Production. Multiple tasks titled as Production appear.
How do I distinguish which task resides in the project I am currently working on? The project name will not appear for sub-tasks. Parent tasks are important for my team as these are identified as our milestones. There have been numerous times where I have selected what I thought was the correct task which then setup a dependency with a task in a separate project. It gets frustrating when I currently have 25+ projects with the same task names and I have to select multiple tasks until I find the correct one. Is there a better way to handle this?
Iniciar sesión para dejar un comentario.