I use the timeline dependencies for tasks related to producing animations and videos. Often a few tasks that are dependant on each other happen on the same day as we get feedback or complete things quickly. On the timeline view the line between these goes red if they are on the same day. Its a small thing, but it would be great if it remained grey and only went red if the dependant task was pushed to a day before.
I have the same concern. I would love that the dependency conflicts only happened when it’s days before and not on the same day.
1 Like
+1 - It’s pretty frequent that a task takes less than one day, so it’s also common that its downstream task would be scheduled for later in the same day. Quick fix in the codebase from > to >=. Thanks!
3 Likes
Yes. needs to be fixed ASAP. Just paid for premium and not happy to find this feature. Most dependant tasks are same day for me. The way it is set up now, 300 tasks would take 300 days.
5 Likes
Our team have the same issue, many task delivered on the same day but still dependent on each other. Hope Asana can implement a quick fix!
1 Like
Same issue here - have lots of tasks that don’t take an entire day to complete but it’s still helpful to put the dependency information in.
It shows the flow of the tasks at day level rather than just at week level
1 Like
Same issue - we must be flexible when accommodating the demands of our clients, which means expediting or shuffling timelines within a project. Within these, we perform multiple tasks on the same day that are dependent on one another.
With the complexity or our templates and amount of ongoing projects, we cannot afford to be manually shifting tasks in timeline view to accommodate this “behaviour” and make sure our timeline still works.
Simply needs automating!
Same here. Our projects involve about 9 sections and always have +200 tasks. Many of those tasks are same day, different assignee. When dragging in timeline view, the majority of tasks are left behind. So uninterested in 3rd party solutions to workaround a basic bug fix of > to >= in codebase.
So, is there still no resolution to this? Also, I’m a total newbie. How do you get a task to be dependent and still on the same day? When I drag them onto the timeline and create the dependency, I cannot get them on the same day, it always moves the prior task back a day.
Within my first hour as a user I ran into this issue, searched endlessly for the workaround, and am disappointed interdependent same day tasks are not permitted. Asana customers live in the real world.
@Kevin_Strite and @James_Conlon,
In the 3-dots menu in the upper right of the Timeline view, turn off the “Prevent dependency conflicts” option. You can then have dependent tasks be placed on the same day.
Thanks for the guidance. You should add this to the discussion where I posted my comment.
Phil, by turning off conflicts, wont the tasks stop moving forward in-sync if an item goes past-due?
Forgive my brevity if the question is confusing, as I am writing while in an Uber haha. Thanks!
1 Like
Well, yes. That’s the trade-off you have to make if you want to be able to have a dependent task be on the same day as its predecessor.
Or… I would be remiss if I didn’t mention that you can avoid the trade-off and have both capabilities if you use the Auto-Adjust Workflow type in my Flowsana integration. That workflow shifts dependent tasks a la Asana’s dependency-shifting, except that it shifts ALL dependencies, not just when there is an overlap, and also it works in ALL views, not just Timeline.
Thank you Phil,
But your solution would mean having to use another piece of software to achieve a most basic function of any project management software: dependencies between tasks. It would add to the complexity of the processes, when the goal of Asana is to reduce complexity, not increase it.
I found out about this a few minutes ago and I’m very surprised.
A very common example: In my experience, there are always a set of stage start-up items that have to be performed upon starting a new stage of a project. They normally involve different parties (PM has to confirm previous all tasks in previous stage were completed correctly - quality control - admin has to check handover documents have been provided in full and accounting has to send invoice and confirm payment, etc). That however, doesn’t take a full day, let alone each of those tasks taking a full day each.
Now, without dependencies between those tasks there is a serious risk of the development/PM teams starting to work at full speed on tasks that won’t actually be approved because upon receiving an invoice for a stage the client decided to review their requirements and expectations, asking for meetings to discuss changes and changing the specifics of the work to be performed (tasks). This is a very common occurrence.
On the other hand, without dependencies, no developer/PM/team leader would receive a notification to start work on that stage after all the above items had been completed. In fact, if that set of stage start-up items were done by 3 different parties (example: accounting, admin, PM) and were dependent on each other (PM has to confirm previous all tasks in previous stage were completed correctly - quality control - admin has to check handover documents have been provided in full and accounting has to send invoice and confirm payment), that actual process would automatically be assessed by Asana as taking a minimum of 3 days (3 different tasks with dependencies between them).
In a busy environment and with very busy schedules and many different parties involved in several different projects running simultaneously, any organization would lose track of where resources should be assigned to and when (reducing productivity considerably) or would risk having teams working on tasks that didn’t actually exist (were never approved by the client).
As a chartered certified consultant, it is my responsibility to advise any organization that I provide my expertise to to choose project management software that doesn’t have any such critical flaw or to advise them to prepare their business to spend a lot of time and money creating “work arounds” and accept the risks of doing so.
Gonçalo → +20y of PM experience PMI PMP, Prince2 practitioner, chartered engineer
I found a work/around that ALMOST works:
create rule - task is no longer blocked>>set due date to “0”
However this only updates the first task and does not activate the “Prevent dependency conflicts” of the timeline view, so other tasks that come after it don’t update their due dates
While in timeline view on a project, it would be helpful to stack multiple dependent tasks together on the same day while maintaining the “prevent conflict dependency” feature that allows tasks to repond to each other’s position when adjusted. Some days I have many tasks dependent on each other that are small and all achievable within a single day, yet currently I have to spread these out over a week or more in the timeline if I utilise "prevent conflict dependencies)
Hi @Rhett_Deighton, welcome to the Asana Community forum 
Thanks for taking the time to share this feedback.
We do have an existing thread for this feature request in the #productfeedback category so I’ve gone ahead and merged your post with the existing one to consolidate feedback.
I’ll keep you posted and let you know if I have any updates 
1 Like
Thanks Rebecca
1 Like
Yea i have some same day dependencies as well. Would love a fix for this
1 Like