It would be incredibly helpful if there was an option to have a project start and end date remain unchanged by maintain buffer or consume buffer on dependent tasks.
The projects I work through and manage have very firm start and end dates, however tasks within the date range may change based on individual team member availability and workflows.
Is there a way that if a dependent task date needs to change, by either maintaining buffer or consuming buffer, the start and end date of a project still remains the same? I don’t mind if some tasks over lap, but my start and end dates need to be static.
Its not helpful to have upstream of downstream tasks push out my start or end dates in these instances where there are firm deadlines.
My experience thus far is that when I have dependent tasks set to either consume buffer, or maintain buffer, it will change my start/due dates for the project. I’m hoping for an update to allow the option make the start/end dates static so that only the tasks in between can change dates.
Maybe you’re talking about dates of tasks (one task representing project start and one task representing project end) whereas I was showing Asana’s built-in dates of projects.
If you’re using two tasks as above, you could remove their dependencies.
Yes, sorry that’s what I was talking about. There are project milestone tasks that serve as a firm deadline within the project, that would benefit me as being static.
Ok, remove their dependencies for each of these tasks and they won’t participate in the date shifts but all the other tasks will continue to participate.
For proper Project Management, there must be a way to anchor Critical Path tasks and be notfied visually if theres risk to critical path anywhere on the timeline.
If Asana is serious about being a project coordination tool or PM tool, this is a very important feature that’s required. Taking the Critical Path items out of the dependency chain doesn’t make any sense to me.
