I don't agree with the suggested solution of entering users vacation days in a different project. This doesn't do anything other than put the resource over capacity.
It does leave one to question what the desired effect would be if a resource was marked as "On Vacation". Two options as I see it:
1. If I have a 5 hour task that spans 5 days @ 1 hour per day, making the assigned resource unavailable might force the time update to 1.25 hours per day such that the work can be consumed in the remaining 4 days.
2. If I have a daily task to "Take out the Garbage" and it occurs every day for 10 minutes. Marking a resource unavailable means that the task won't be completed that day and therefore shouldn't be calculated into that work item's total.
Assuming any development is being done on this (doesn't look like there is based on the age of the thread), I imagine each task would need some sort of flag that would indicate how the work item is handled when a resource goes OOO.
I don't agree with the suggested solution of entering users vacation days in a different project. This doesn't do anything other than put the resource over capacity.
It does leave one to question what the desired effect would be if a resource was marked as "On Vacation". Two options as I see it:
1. If I have a 5 hour task that spans 5 days @ 1 hour per day, making the assigned resource unavailable might force the time update to 1.25 hours per day such that the work can be consumed in the remaining 4 days.
2. If I have a daily task to "Take out the Garbage" and it occurs every day for 10 minutes. Marking a resource unavailable means that the task won't be completed that day and therefore shouldn't be calculated into that work item's total.
Assuming any development is being done on this (doesn't look like there is based on the age of the thread), I imagine each task would need some sort of flag that would indicate how the work item is handled when a resource goes OOO.