I am having an issue with due dates not changing for tasks that are dependent on the one I changed.
Okay so we have Projects that have will have Fabrication tasks that our production dept will see in their Master Schedule (these tasks live in 2 places their Actual Project and shared to Master Schedule - see image 1). What you can see in the task details is this task is a blocking task “Package Panels and Hardware” but you don’t see it in the gantt view because it doesnt belong in this area.
The issue we are running into is, if my production manager needs to change a due date to this task and they change it in the Master Schedule project by any amount of days, the task it is blocking does not move out in the Main Project, and we run into schenarios where “Package Panels and Hardware” are now scheduled before we are going to be done the task it is dependent on.
Is there a reason this doesn’t automatically happen?
Dependency shifting is only supported within a project; it does not work across projects. That’s Asana’s design at the moment. See for example Dependency Management and Multihomed Tasks.
(Alternate solution: use the Auto-adjust Workflow in our Flowsana integration which works across projects. )
Yeah that would be great. I feel like even if the task is listed in 2 projects if it has any dependency it should move those no matter what the view is, they are linked no matter what not because of what project you are viewing it in.
@Adam_Rahmani I’ve moved it, and you can now vote for it.
Although I like the idea, it might not be straightforward to solve this. Currently it’s hard to have conflicting dependency settings. But which dependency settings should be chosen when more than one can be applied? And should this be chosen automatically? Should the user be queried about this?
)