Forum Discussion
Solved
Task should not be started on weekend but can run continuously during weekend
I have several tasks that takes 18 to 25 days in row. Those tasks should be started from Monday to Friday. I could not made a schedule for those tasks
Or......how about this "end around run"? As soon as the "milestone" takes on a non-zero value, the Monday through Thursday only custom calendar as the Task Calendar does the trick.
John 🙂
Ignacio --
I hereby give you the "I Corrected Dale Howard MVP" award for catching my erroneous response to this question. I thank you for correcting my mistake. You are indeed correct that the Task Calendar has NO EFFECT on milestone tasks. Well done, my friend! I think the user should refer to your post about breaking up the task in question. Hope this helps.
I hereby give you the "I Corrected Dale Howard MVP" award for catching my erroneous response to this question. I thank you for correcting my mistake. You are indeed correct that the Task Calendar has NO EFFECT on milestone tasks. Well done, my friend! I think the user should refer to your post about breaking up the task in question. Hope this helps.
Or......how about this "end around run"? As soon as the "milestone" takes on a non-zero value, the Monday through Thursday only custom calendar as the Task Calendar does the trick.
John 🙂
- Great. Thank you very much. It works.
- Dale,
My take is a milestone should not be called task, just like a summary is are not task. Unfortunately I see many users, mostly newbies, who don't quite understand this. So I threw in the 1 minute duration "milestone" to create a true task and then your approach works fine.
Although I can see the advantage of having calendar control over a milestone, (present case in point), I can also see some logic in not having milestones responsive to calendars.
It's interesting, I haven't seen any feedback from the original poster. Maybe we confused him and now he's not sure what to do.
John - John -- It makes no sense that a Task Calendar will not override the schedule of a milestone task. But if memory serves me correctly, this has been the default behavior of Microsoft Project for a long time, which Ignacio reminded me about. I would call this sloppy design, but it is what it is. 😞
