TL;DR - Changes to due dates on tasks with dependencies across different projects should update due dates of dependent tasks in all projects (or pop out a modal asking user to approve date changes in other projects).
My use case: I have projects with many components. Sometimes, individual components will spawn new projects that have a few tasks/milestones multi-homed back to the original project.
My ask: I would like those multi-homed projects to have dependencies in both the origination and the spinoff project. When a multi-homed task’s due date is updated in either project, I would like those changes to be reflected in both projects’ dependent tasks.
I have read this forum post, which leads me to believe that (as of '22) this functionality is not supported (without using Flowsana, which is unfortunately not possible for my org).
Does anyone have any workarounds (or best practices for process) that they have implemented with their teams to allow this type of cross-project collaboration?
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?
Currently (if your dependency settings are set for this), if you change a due date for a task within a project, it affects the due dates of downstream dependencies. However, when I change a due date from “My Tasks”, no dependent tasks are affected. Is it possible to change settings so that the dependencies are affected from the “My Tasks” tab, not just the projects themselves?
My team uses My Tasks to manage our workloads across projects and it’s messing up our projects to not have this feature. Has this been a problem for anyone else?
It is actually not related to My Tasks but rather “changing a date on a task will only shift in the same project” so if you update a task from a project A, if the task is also in project B, I believe it won’t shift there. My Tasks here is considered to be a “project” of some sort. At least that’s my current understanding.
At the moment that’s a know limitation but you were correct to create a Product Feedback, make sure to upvote it.
I’ve merged this topic into an existing one where you can click the title to scroll to the top and vote by clicking the Vote button at the top-left. Existing votes will be merged.
a task is multihomed in two projects, and in each one it has different other tasks linked with dependencies. When the main task is rescheduled while looking at the project A, only the dependent tasks in project A shift properly, while the tasks in project B stand still, causing an overlap.
Why don’t all dependent task move, regardless of which project am i viewing? It doesn’t make sense.
Yes, i know i might create a big project with all the dependent task in there, but it’s not feasible in my case and it’s a workaround, not a solution.
FYI the Auto-adjust Workflow in our Flowsana integration works the way you expect: it will update dependent tasks no matter what project(s) they are in.
Thanks Phil, I appreciate it but it’s something that should be as default.
Moreover, i come across this answer way too many times in this forum: it’s a good sign for you, meaning you can solve many problems, but a very bad sign for Asana.
I’ve just finally started using dependencies and quickly came up against this problem. My team move their tasks around daily from their list or calendar views - it’s very odd that Asana have decided this won’t move the dependent tasks. I can go into the project view and reschedule from there I suppose, but this seems like a crazy thing to leave out!
)