I am testing out a new project template where the Project Constraints are ASAP, but some of the tasks are ALAP. I am making the assumption that the ALAP tasks should take the end date of the milestone they are under, but they are taking the end date of the entire project. Is this a bug, or is this the proper function of the constraint?
Please sign in to leave a comment.
Hello Kristin,
I think this is by design. It seems contradictory putting ALAP tasks in ASAP milestones. What is the behaviour you expect when the milestone is ASAP with no dates manually set and the task is ALAP? I would expect the task to be either scheduled at the latest date of the project (what we see) or at the beginning of the milestone (same as ASAP).
Roland
For our projects, all tasks are dependent on the dates of the middle milestone (milestone named 'inspection' in this example). ASAP is okay for the 'inspection milestone' and anything after, but the tasks in the first milestone just need to be completed before the 'inspection milestone' starts (which would fall in the ALAP category)
Up until now, we have been operating under ASAP. This causes our projects to show as 'off track' all the time because if they aren't completed on day 1 of the first milestone, then they are overdue.
Clarizen does not support scheduling like this based of of a middle date where half the project is ALAP or half is ASAP. You can mix these to some extent with moderation, but you cannot have one central date the will drive the project in both directions.