I haven't been using the Resource Leveling because of limitations I discovered a couple of years ago when we bought WF. The one you described is true, it'll only level the Primary assignment on the task. There was another one that was weird. If you had ANY task in your Project set to a Duration Type of Effort Driven, the Resource Leveling would not work (and wouldn't warn you) – they had this in their documentation. We were warned from Day 1 by a WF Tech (back in December 2014) that the leveling didn't work very well. But as far as I know these were the two biggest constraints. To address this same type of issue when working with MS Project and it's integration with TFS (had the same constraint with leveling – couldn't handle multiple resources) I simply started assigning only one person per task. So in some cases I had to duplicate a task. But actually since they're usually doing different things on a task it didn't happen as often as you'd think. This actually turned out to be a decent practice from a PM perspective anyway. I found when I have multiple people assigned to a task, it can cause confusion and churn on the task. If I have one person assigned I can make it more finite and descriptive and more clear as to what "done" looks like. So assigning one person per task didn't bother me as much as I thought it would. But yes it's inconvenient and MS Project (when not integrated with TFS) can still level with multiple resources – which I think is where WF needs to get eventually. Vic Alejandro, PMP, CSM | IT | Sr. IT Project Manager Denver Water | t: (303-628-7262) | c: (303-319-6473) "http://www.denverwater.org/">
http://www.denverwater.org INTEGRITY | VISION | PASSION | EXCELLENCE | RESPECT