Forum Discussion
Task should not be started on weekend but can run continuously during weekend
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 🙂
Here's one approach.
1. Create a "start" milestone that uses the Standard calendar (M-F) for each of the continuous tasks.
2. For those tasks that may run 24/7, set their Task Calendar to the built-in "24 hours".
3. Make the start milestone the predecessor to the continuous tasks.
Note, if most of the tasks in your plan use the Standard calendar, the start milestones will automatically take on the Standard calendar, but if your plan has a separate custom calendar (e.g. 9 hour days, etc.), then set the Task Calendar for each milestone to be the Standard calendar.
Hope this helps.
John
Hi
I think that using the milestone as a predecessor does not prevent its successor task from starting on Saturday or Sunday, because since the milestone has a duration of 0 days, it will not be affected by any calendar.
Perhaps dividing the continuous task from Monday to Sunday, with Jhon's idea, into Start task A (1d/Calendar Monday to Friday)) and Remaining task A (Dur-1/Calendar Monday to Sunday), linked Finish-Start.
Still, there may be exceptions where this approach may not be appropriate and would require review.
Regards.
Ignacio MartÃn
- Ignacio Martin,
Yes, you are correct, I didn't test out my approach before posting. The approach you suggest will of course work but I think a more robust solution is with a macro.
John- John --
In response to Martin's reply, I DO think that using a milestone would be a workable solution. However, the milestone would need a custom calendar applied to it that only schedules work to take place from Monday through Thursday only, but not on a Friday. This would allow the successor task to start from Monday through Friday, but NOT on a Saturday or Sunday. Your solution was so close! Just a thought. Hope this helps.
