I would use task usage and resoource usage and resource graph views to find out exactly which tasks, which day/time Dave is over-allocated.
You may have a mistake in the timing of the recurring tasks which is allowing them to overlap. You need to have a date/time format which shows the times as well as the dates.
if you clicked on the level button without checking leveling options, it may be that there is only a short period of over-allocation, maybe 1 minute, and if in leveling options there is "day by day" then the resolution won't catch it.
The problem with using recurring tasks is that it imposes a date constraint on every task. The recurring tasks feature basically does nothing more than create a rack of tasks with SNET date/time constraints.
Once you have created the tasks with the date constraints there is not much point in linking tasks in one group to tasks in another.
It is not a great idea to try to fix resource over-allocation by linking tasks as predecessor/successor when those tasks are not connected to each other except that they are competing for the same resource.
I would not use recurring tasks fior this. I would make a calendar with Friday the only working day, and have a task named "visit building 1", 60m, and assign the calendar to the task, make 50 of those (for 50 weeks). Repeat for the other buildings. You get 350 tasks, don't link any of them, assign Dave, then level.
Member for
19 years 11 monthsChristine,I would use task
Christine,
I would use task usage and resoource usage and resource graph views to find out exactly which tasks, which day/time Dave is over-allocated.
You may have a mistake in the timing of the recurring tasks which is allowing them to overlap. You need to have a date/time format which shows the times as well as the dates.
if you clicked on the level button without checking leveling options, it may be that there is only a short period of over-allocation, maybe 1 minute, and if in leveling options there is "day by day" then the resolution won't catch it.
The problem with using recurring tasks is that it imposes a date constraint on every task. The recurring tasks feature basically does nothing more than create a rack of tasks with SNET date/time constraints.
Once you have created the tasks with the date constraints there is not much point in linking tasks in one group to tasks in another.
It is not a great idea to try to fix resource over-allocation by linking tasks as predecessor/successor when those tasks are not connected to each other except that they are competing for the same resource.
I would not use recurring tasks fior this. I would make a calendar with Friday the only working day, and have a task named "visit building 1", 60m, and assign the calendar to the task, make 50 of those (for 50 weeks). Repeat for the other buildings. You get 350 tasks, don't link any of them, assign Dave, then level.